MonitorWare Knowledge Base

Not so much a question as much as a warning to current users upgrading. If you have disk caching/queing enabled when you update your binary, you have to pop your cache files (the .qi and the .00000001) for rsyslog to start again.

my debug snippet....

6075.847307205:main queue:DA/w0: main queue[DA]: I am a child
6075.847416501:main queue:DA/w0: 6075.847416959:strm 0x85a54f8: main thread: FF opened file '/var/log/rsyslog.buffer.qi' for READ (0x0) as 5
6075.847599587:main queue:DA/w0: strm 0x85a54f8: FF file 5 read 523 bytes
6075.847642869:main queue:DA/w0: strm 0x85a54f8: file 5 closing
6075.847672139:main queue:DA/w0: main queue[DA]: error -2028 reading .qi file - can not read persisted info (if any)
6075.847695821:main queue:DA/w0: main queue[DA]: persisting queue to disk, 0 entries...

Thanks for all the work done on this project.

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

Oh, that's a good point. I changed the serialization but did not do the proper version check (there is a serialization encoding version inside the disk files, but I did not increment/check it... ).

Thanks for pointing it out.

Rainer

Oh, and I noticed one thing. You specifically mention the .000001 file. What queue mode do you use? I am asking because it looks like "disk" mode, but most people do not really need to use disk. The in-memory queue modes automatically go to disk if (and only if) they need to e.g. when the memory queue limit is reached or rsyslogd is shutdown. This offers by far superior performance over disk mode. I thought I ask

Rainer

It wrote a .000001 file because i shut down the daemon to do the upgrade ( i have $MainMsgQueueSaveOnShutdown enabled).

very well - I just thought I drop that extra bit of information. I have noticed that a lot of folks use "disk" mode because it sounds like it need to be used when going to disk (what is wrong, as outlined above).

Thanks again for making all aware of the original problem!

Rainer