Knowledge Base & Discussion Forum

AhsayUBS Server - root: Failed to send status report [SOLVED]

Discuss technical questions on AhsayUBS

Moderator: Support Team

AhsayUBS Server - root: Failed to send status report [SOLVED]

Postby jimmurdoch » Mon Jun 22, 2015 4:08 pm

Hi,
On my UBS I am getting the following error in the log:

Jun 22 09:46:57 root: Failed to send status report to: email@address.
Jun 22 09:46:57 kernel: pid 83155 (php), uid 0 inumber 13385 on /: filesystem full
Jun 22 09:46:57 root: Error: Failed to create '/ubs/runtime/email.status'.

This is generated everytime the system attempts to send an email.

Free disk Space displays the following:

Free disk space
Filesystem Size Used Avail Capacity Mounted on
/dev/md0 123M 123M 150k 100% /
/dev/md1 15M 210k 13M 1% /var
/dev/mirror/2EEDF0EFxesfmfw 739M 612M 67M 90% /ubs/mnt/esfmfw
/dev/mirror/2EEDF0EFxesosfw 185M 83M 87M 49% /ubs/mnt/esosfw
devfs 1.0k 1.0k 0B 100% /dev
eslsfwx2EEDF0EF 889G 165G 724G 19% /ubs/mnt/eslsfw

Any help appreciated.
Thanks,
Jim
jimmurdoch
 
Posts: 28
Joined: Mon Sep 15, 2014 6:07 pm

Re: root: Failed to send status report

Postby Support2 » Mon Jun 22, 2015 5:32 pm

Hello Jim.

It looks the space in the root partition mounted on /dev/md0 has been used up. Normally there should around 27 MB free for use. In most cases it is either the /var/tmp or /var/log folder which contains the FreeBSD temporary files and logs files which causes this problem.

To verify if this is the case can you run the following commands and post the results? So we can determine what the next step is going to be.

1. du -sh /var/log
2. du -sh /var/tmp

Normally both folders combined should contain less than 1 MB of data.
User avatar
Support2
 
Posts: 390
Joined: Thu Oct 18, 2007 5:53 pm

Re: AhsayUBS Server - root: Failed to send status report

Postby jimmurdoch » Mon Jun 22, 2015 6:25 pm

Thanks. Here are the results:

ahsayubs:~# du -sh /var/log
8.0k /var/log
ahsayubs:~# du -sh /var/tmp
0B /var/tmp
jimmurdoch
 
Posts: 28
Joined: Mon Sep 15, 2014 6:07 pm

Re: AhsayUBS Server - root: Failed to send status report

Postby Support2 » Wed Jun 24, 2015 9:22 am

Hello Jim,

Thank you for getting back to us.

As the space issue is not caused by the usual problem of log file filling the the /var/log or temporary files not been removed proplery in /var/tmp folders.

The next step is to rule out any possible disk or ZFS volume related issues on the AhsayUBS server? You can do this by looking at system log in your AhsayUBS web admin console under [Information]>[System Logs] for any errors or using dmesg in command line.

To check the health of the ZFS volume you can use the zpool status command

Please let us know the results
User avatar
Support2
 
Posts: 390
Joined: Thu Oct 18, 2007 5:53 pm

Re: AhsayUBS Server - root: Failed to send status report

Postby jimmurdoch » Wed Jun 24, 2015 2:50 pm

Hi, The only log errors are those I already posted.

The zpool status is as follows:

ahsayubs:~# zpool status
pool: eslsfwx2EEDF0EF
state: ONLINE
scan: scrub repaired 0 in 0h58m with 0 errors on Sun Jun 21 00:58:23 2015
config:

NAME STATE READ WRITE CKSUM
eslsfwx2EEDF0EF ONLINE 0 0 0
label/2EEDF0EFxd00p09 ONLINE 0 0 0
label/2EEDF0EFxd01p09 ONLINE 0 0 0
logs
mirror-2 ONLINE 0 0 0
label/2EEDF0EFxd00p07 ONLINE 0 0 0
label/2EEDF0EFxd01p07 ONLINE 0 0 0

errors: No known data errors

Running dmesg returns a series of rows which flows off the screen, all showing filesystem full:

pid 7222 (php), uid 0 inumber 13385 on /: filesystem full
pid 15957 (php), uid 0 inumber 13385 on /: filesystem full
pid 24773 (php), uid 0 inumber 13385 on /: filesystem full
pid 33508 (php), uid 0 inumber 13385 on /: filesystem full
pid 42243 (php), uid 0 inumber 13385 on /: filesystem full
pid 50978 (php), uid 0 inumber 13385 on /: filesystem full
pid 59713 (php), uid 0 inumber 13385 on /: filesystem full
pid 68448 (php), uid 0 inumber 13385 on /: filesystem full
pid 77183 (php), uid 0 inumber 13385 on /: filesystem full
pid 85998 (php), uid 0 inumber 13385 on /: filesystem full
pid 94733 (php), uid 0 inumber 13385 on /: filesystem full
bge0: link state changed to DOWN
bge0: link state changed to UP
pid 3592 (php), uid 0 inumber 13385 on /: filesystem full
pid 12327 (php), uid 0 inumber 13385 on /: filesystem full
pid 21062 (php), uid 0 inumber 13385 on /: filesystem full
pid 29797 (php), uid 0 inumber 13385 on /: filesystem full
pid 38532 (php), uid 0 inumber 13385 on /: filesystem full
pid 47347 (php), uid 0 inumber 13385 on /: filesystem full
pid 56082 (php), uid 0 inumber 13385 on /: filesystem full
pid 64817 (php), uid 0 inumber 13385 on /: filesystem full
pid 73552 (php), uid 0 inumber 13385 on /: filesystem full
pid 82287 (php), uid 0 inumber 13385 on /: filesystem full
pid 91024 (php), uid 0 inumber 13385 on /: filesystem full
pid 99759 (php), uid 0 inumber 13385 on /: filesystem full
pid 8690 (php), uid 0 inumber 13385 on /: filesystem full
pid 17425 (php), uid 0 inumber 13385 on /: filesystem full
pid 26160 (php), uid 0 inumber 13385 on /: filesystem full
pid 34899 (php), uid 0 inumber 13385 on /: filesystem full
pid 43634 (php), uid 0 inumber 13385 on /: filesystem full
pid 52369 (php), uid 0 inumber 13385 on /: filesystem full
pid 61104 (php), uid 0 inumber 13385 on /: filesystem full
pid 69919 (php), uid 0 inumber 13385 on /: filesystem full
pid 78654 (php), uid 0 inumber 13385 on /: filesystem full
pid 79934 (php), uid 0 inumber 13385 on /: filesystem full
pid 83155 (php), uid 0 inumber 13385 on /: filesystem full
pid 92065 (php), uid 0 inumber 13385 on /: filesystem full
pid 902 (php), uid 0 inumber 13385 on /: filesystem full
jimmurdoch
 
Posts: 28
Joined: Mon Sep 15, 2014 6:07 pm

Re: AhsayUBS Server - root: Failed to send status report

Postby jimmurdoch » Wed Jun 24, 2015 5:38 pm

Hi,

A reboot seems to have corrected the problem:

Filesystem Size Used Avail Capacity Mounted on
/dev/md0 123M 96M 27M 78% /
/dev/md1 15M 210k 13M 1% /var
/dev/mirror/2EEDF0EFxesfmfw 739M 612M 67M 90% /ubs/mnt/esfmfw
/dev/mirror/2EEDF0EFxesosfw 185M 83M 87M 49% /ubs/mnt/esosfw
devfs 1.0k 1.0k 0B 100% /dev
eslsfwx2EEDF0EF 889G 165G 724G 19% /ubs/mnt/eslsfw

Thanks.
jimmurdoch
 
Posts: 28
Joined: Mon Sep 15, 2014 6:07 pm

Re: AhsayUBS Server - root: Failed to send status report [SOLVED]

Postby Support2 » Thu Jun 25, 2015 9:49 am

Hello Jim,

Thanks for updating us. Glad everything has worked out.

The reboot of your AhsayUBS may have cleared some temporary system files or logs from the other folders on the root partition other than /var/log and /tmp so freeing disk space.

If this problem re-occurs please check the disk usage on the other folders on the root partition, i.e. /etc, /mnt, /usr, /ubs, /root etc to try to narrow the problem..
User avatar
Support2
 
Posts: 390
Joined: Thu Oct 18, 2007 5:53 pm


Return to AhsayUBS

Who is online

Users browsing this forum: No registered users and 1 guest

Looking for Rbackup Alternative | Vembu Alternative | Novastor Alternative | Asigra Alternative | BackupAgent Alternative? Try our product.


A wholly owned subsidiary of Ahsay Backup Software Development Company Limited  [HKEx Stock Code: 8290]