Dear community,

Due to a memory leakage in one docker i ran out of ram. As a result the syslog stopped logging. The docker issue has been resolved, but syslog remained silent.

How do I restart syslog? I know the easy way is to restart the Unraid but I would like to avoid this step.

 

 

Make sure you have room ion the temp filesystem used for logging. What does "df -h" indicate for the /var/log section? I suspect you ran out of room there too.

Thank you for your input BRiT,

You are right:

tmpfs          128M  128M    0 100% /var/log

Obviously went out of room.

What is causing this and how to resolve it?

My unraid is living on a 8GB flash drive and have a lot of space in there.

 

I'm pretty sure this is a known issue and was slated to be fixed in the next beta. Have to have LT confirm that to be sure.

Thank you for your comment, archedraft.

Hope it will be fixed in the next beta.

Does this means there is no way the syslog to be restarted from command line?

 

Thank you for your comment, archedraft.

Hope it will be fixed in the next beta.

Does this means there is no way the syslog to be restarted from command line?

 

There is a way of doing so. I dont recall off hand if its using "/etc/rc.d/syslog restart" or just using the syslog daemon with a restart or sending a HUP signal.

 

Theres also a means of remounting the tmpfs /var/log using more memory, such as 256 MB.

Thanks BRiT

Unfortunately the command doesn't work

root@UNRAID:~# /etc/rc.d/syslog restart

-bash: /etc/rc.d/syslog: No such file or directory

Thanks BRiT

Unfortunately the command doesn't work

root@UNRAID:~# /etc/rc.d/syslog restart

-bash: /etc/rc.d/syslog: No such file or directory

 

Yeah, I didn't know what the actual filename was, but I just dove into the zip file (I'm remote and not at my server). Try the following:

 

/etc/rc.d/rc.rsyslogd restart

 

You will still need to clear up space.

 

Fyi: it also has a reload command, so if you change its configuration that would be used.

Thank you for your comment, archedraft.

Hope it will be fixed in the next beta.

Does this means there is no way the syslog to be restarted from command line?

 

This happened to me and I just restarted my server. It takes awhile for my log to fill up so I do not mind restarting my server every week or so (I am messing with it so much anyways, that I normally restart it more than a few times a week anyhow).

I put this in my go script.  It resizes your tmpfs 256 instead of 128.

# resize tmpfs
mount -o remount,size=256m /var/log

 

Thank you all for your comments.

Best regards.