/var: filesystem full - Server stopped working

Status
Not open for further replies.
Joined
Jan 10, 2014
Messages
1
I have a big problem with our freeNAS Server. Monday it stopped working.
The log looked like this before i rebooted:

Code:
Jan  6 16:24:55 Storage kernel: pid 10224 (smbd), uid 0 inumber 9314 on /var: filesystem full
Jan  6 16:24:55 Storage kernel: pid 10217 (nmbd), uid 0 inumber 9273 on /var: filesystem full
Jan  6 16:25:00 Storage kernel: pid 1789 (syslogd), uid 0 inumber 9315 on /var: filesystem full
Jan  6 16:25:02 Storage kernel: pid 12696 (python), uid 0 inumber 34345 on /var: filesystem full
Jan  6 16:25:05 Storage kernel: pid 10217 (nmbd), uid 0 inumber 9273 on /var: filesystem full
Jan  6 16:25:15 Storage kernel: pid 10217 (nmbd), uid 0 inumber 9273 on /var: filesystem full
Jan  6 16:25:21 Storage kernel: pid 12678 (smbd), uid 0 inumber 9314 on /var: filesystem full
Jan  6 16:25:25 Storage kernel: pid 10217 (nmbd), uid 0 inumber 9273 on /var: filesystem full


After the reboot everthing worked well again. but i found out that the nmbd and smbd log file is very big and it gets bigger every day.
so how can i limit the size of the nmbd/smbd log to prevent these crashes? How can i set down the log level?

Any help is appreciated!!
 
D

dlavigne

Guest
Depending upon your FreeNAS version, you can also create a dataset named syslog so that the logs are automatically stored on the disks rather than the OS drive.
 

Yatti420

Wizard
Joined
Aug 12, 2012
Messages
1,437
Depending upon your FreeNAS version, you can also create a dataset named syslog so that the logs are automatically stored on the disks rather than the OS drive.


Does it store it on disk instead of USB/ramdisk? Not both? I didn't know this could be done.. An addition for the docs?
 
Status
Not open for further replies.
Top