You are not logged in.

#1 2012-11-22 08:26:23

wolfdogg
Member
From: Portland, OR, USA
Registered: 2011-05-21
Posts: 545

log wierdness

1) i was looking to view my cron log to see if rsnapshot just ran, and i see that both crond.log is 0 bytes, and so is crond.log.1, then i notice that all the error logs ending in .log, and log.1 are 0 bytes.  this might have something to do wtih the fact that its just past midnight local time, or something went wrong with error logging.  The last date on the error logs(ones that contain data, ending in 2) are Nov 7th.  Wheres my cron logs?

2) my everything.log.2, which is the only other one i tried viewing so far, is 8,483,082+ lines long and for every entry there is 4 lines of duplicates.  can someone tell me where i can look to adjust / fix this?  it looks like the bulk of the last 20 000 messages are related to postfix, and ill bet it is a large chunk of them.  im still setting that up for the last couple weeks, so thats not really an issue.  what i cant figure out is why the system is repeating entries.

Last edited by wolfdogg (2012-11-22 08:28:32)


Node.js, PHP Software Architect and Engineer (Full-Stack/DevOps)
GitHub  | LinkedIn

Offline

#2 2012-11-22 10:36:21

loafer
Member
From: the pub
Registered: 2009-04-14
Posts: 1,772

Re: log wierdness

1)  Have you switched to systemd?  If so use journalctl.  The old, unused logs will be empty in this case.  Unless you configure systemd to use syslog of course.

2)  I do not know how postfix logs so i cannot comment.


All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.

Offline

#3 2012-11-22 14:01:29

fsckd
Forum Fellow
Registered: 2009-06-15
Posts: 4,173

Re: log wierdness

Moving from Arch Discussion to Applications & Desktop Environments.


aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies

Offline

#4 2012-11-22 17:28:25

MadTux
Member
Registered: 2009-09-20
Posts: 553

Re: log wierdness

wolfdogg wrote:

what i cant figure out is why the system is repeating entries.

Can you give examples of duplicate log entries, because it is a bit difficult to analyse without knowing exactly about the problem.

Offline

#5 2012-11-24 08:25:19

wolfdogg
Member
From: Portland, OR, USA
Registered: 2011-05-21
Posts: 545

Re: log wierdness

loafer wrote:

1)  Have you switched to systemd?  If so use journalctl.  The old, unused logs will be empty in this case.

i havent messed with systemd, i just update arch regularly, and am not familiar much on how to pull logs this way.  i did try a few journalctl commands to no avail
including

journalctl -u crond

nothing returned.

also,you mention that old unused logs are empty, but im having the opposite, the brand new logs are empty, not the old ones.  so for example, everything.log (nov 18 - 0 bytes), eveything.log1(nov 11 - 0 bytes), everything.log2(nov 22 - 1101098420 bytes), everything.log3 (nov 4 - 655031139 bytes)
hmm.  just noticed, why is the everything.log1 older than everything.log2, oh, probably because i made a write to it when checking it.

MadTux wrote:

Can you give examples of duplicate log entries, because it is a bit difficult to analyse without knowing exactly about the problem.

Nov  7 21:16:12 postfix/postfix-script[26494]: stopping the Postfix mail system
Nov  7 21:16:12 postfix/postfix-script[26494]: stopping the Postfix mail system
Nov  7 21:16:12 postfix/postfix-script[26494]: stopping the Postfix mail system
Nov  7 21:16:12 postfix/postfix-script[26494]: stopping the Postfix mail system
Nov  7 21:16:12 postfix/master[28018]: terminating on signal 15
Nov  7 21:16:12 postfix/master[28018]: terminating on signal 15
Nov  7 21:16:12 postfix/master[28018]: terminating on signal 15
Nov  7 21:16:12 postfix/master[28018]: terminating on signal 15
Nov  7 21:16:14 nmbd[1097]: [2012/11/07 21:16:14.771234,  0] nmbd/nmbd.c:66(terminate)
Nov  7 21:16:14 nmbd[1097]: [2012/11/07 21:16:14.771234,  0] nmbd/nmbd.c:66(terminate)
Nov  7 21:16:14 nmbd[1097]: [2012/11/07 21:16:14.771234,  0] nmbd/nmbd.c:66(terminate)
Nov  7 21:16:14 nmbd[1097]: [2012/11/07 21:16:14.771234,  0] nmbd/nmbd.c:66(terminate)
Nov  7 21:16:14 nmbd[1097]:   Got SIGTERM: going down...
Nov  7 21:16:14 nmbd[1097]:   Got SIGTERM: going down...
Nov  7 21:16:14 nmbd[1097]:   Got SIGTERM: going down...
Nov  7 21:16:14  nmbd[1097]:   Got SIGTERM: going down...
Nov  7 21:16:15 xinetd[753]: Exiting...
Nov  7 21:16:15 xinetd[753]: Exiting...
Nov  7 21:16:15 xinetd[753]: Exiting...
Nov  7 21:16:15 xinetd[753]: Exiting...
Nov  7 21:16:18 syslog-ng[405]: syslog-ng shutting down; version='3.3.6'
Nov  7 21:16:18 syslog-ng[405]: syslog-ng shutting down; version='3.3.6'
Nov  7 21:16:18 syslog-ng[405]: syslog-ng shutting down; version='3.3.6'
Nov  7 21:16:18 syslog-ng[405]: syslog-ng shutting down; version='3.3.6'
fsckd wrote:

Moving from Arch Discussion to Applications & Desktop Environments.

this seems a core issue, and i do not have a DE, and the post got moved to Applications and DE.  i literally could not find a category to put this post in.  there seems to be a missing category for core issues not related to hardware.

Last edited by wolfdogg (2013-03-20 20:54:54)


Node.js, PHP Software Architect and Engineer (Full-Stack/DevOps)
GitHub  | LinkedIn

Offline

Board footer

Powered by FluxBB