View previous topic :: View next topic |
Author |
Message |
meulie l33t
Joined: 17 Jun 2003 Posts: 845 Location: a Dutchman living in Norway
|
Posted: Mon Jan 26, 2009 8:18 am Post subject: syslog-ng warning |
|
|
Hi all!
I just upgraded syslog-ng 2.0.9 -> 2.1.3, and now I get the following error when starting:
Code: | * Starting syslog-ng ...
Persistent configuration file is in invalid format, ignoring; [ ok ] |
Does anyone here know about changes in the configuration file format between 2.0.x & 2.1.x? _________________ Greetz,
Evert Meulie |
|
Back to top |
|
|
jenkler Apprentice
Joined: 28 Apr 2003 Posts: 223 Location: Sweden - Stockholm
|
Posted: Mon Jan 26, 2009 10:20 am Post subject: |
|
|
nope same here, we need to look into this :D
EDIT: now its gone? Restarted the service but now it seams to work, can someone tell us why?
/J _________________ Hello from me: Jenkler IT AB (swedish) (use google translate). Check out my Linux manpages for web in english. |
|
Back to top |
|
|
meulie l33t
Joined: 17 Jun 2003 Posts: 845 Location: a Dutchman living in Norway
|
Posted: Mon Jan 26, 2009 10:24 am Post subject: |
|
|
When I Google "Persistent configuration file is in invalid format" (with quotes) I get no hits whatsoever, so this must be a recent thing... _________________ Greetz,
Evert Meulie |
|
Back to top |
|
|
jenkler Apprentice
Joined: 28 Apr 2003 Posts: 223 Location: Sweden - Stockholm
|
Posted: Mon Jan 26, 2009 10:25 am Post subject: |
|
|
"Persistent configuration file is in invalid format, ignoring;"
If you do this:
/etc/init.d/syslog-ng pause
/etc/init.d/syslog-ng start
does the error fly away ? _________________ Hello from me: Jenkler IT AB (swedish) (use google translate). Check out my Linux manpages for web in english. |
|
Back to top |
|
|
aztech Tux's lil' helper
Joined: 29 Jul 2002 Posts: 130 Location: Stenungsund, Sweden
|
Posted: Mon Jan 26, 2009 10:48 am Post subject: |
|
|
I'm having the same "problem" with this.
...
Correction, I HAD the same problem when running "syslog-ng restart"
But now after doing a syslog-ng stop && syslog-ng start, the problem
is gone. .. All works fine =) |
|
Back to top |
|
|
meulie l33t
Joined: 17 Jun 2003 Posts: 845 Location: a Dutchman living in Norway
|
Posted: Mon Jan 26, 2009 11:07 am Post subject: |
|
|
aztech wrote: | Correction, I HAD the same problem when running "syslog-ng restart"
But now after doing a syslog-ng stop && syslog-ng start, the problem
is gone. .. All works fine =) |
Same here... Weird... _________________ Greetz,
Evert Meulie |
|
Back to top |
|
|
libertytrek Apprentice
Joined: 18 Jul 2007 Posts: 258
|
Posted: Wed Jan 28, 2009 2:04 pm Post subject: |
|
|
Same here... |
|
Back to top |
|
|
selig Guru
Joined: 31 Jul 2005 Posts: 425 Location: Prague, Czech Republic
|
Posted: Wed Jan 28, 2009 6:42 pm Post subject: |
|
|
When the system boots up, the error gets displayed... when I stop and start syslog-ng, the error is still there but when I pause and start it, it is gone. Really strange. |
|
Back to top |
|
|
user Apprentice
Joined: 08 Feb 2004 Posts: 214
|
Posted: Wed Jan 28, 2009 8:29 pm Post subject: |
|
|
Hi,
syslog-ng increase syslog-ng.persist internal version flag.
After first re-load it is fixed/updated.
So no worry.
before:
Code: |
# cat /var/lib/syslog-ng.persist
SLP1affile_sd_curpos(/proc/kmsg)0
|
after:
Code: |
# cat /var/lib/syslog-ng.persist
SLP2affile_sd_curpos(/proc/kmsg)0
|
|
|
Back to top |
|
|
|