Sometimes when I update my plugins via the plugin manager I get this error message.

 

/usr/local/sbin/plugin update dynamix.cache.dirs.plg 2>&1
plugin: running: 'anonymous'
cache_dirs stopped
plugin: creating: /boot/config/plugins/dynamix.cache.dirs/dynamix.cache.dirs-2015.04.28.txz - downloading from URL https://raw.github.com/bergware/dynamix/master/archive/dynamix.cache.dirs-2015.04.28.txz
plugin: running: /boot/config/plugins/dynamix.cache.dirs/dynamix.cache.dirs-2015.04.28.txz

+==============================================================================
| Installing new package /boot/config/plugins/dynamix.cache.dirs/dynamix.cache.dirs-2015.04.28.txz
+==============================================================================

Verifying package dynamix.cache.dirs-2015.04.28.txz.
expr: syntax error
/sbin/installpkg: line 432: [: -lt: unary operator expected
/sbin/installpkg: line 434: [: -lt: unary operator expected
expr: syntax error
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 466: echo: write error: No space left on device
/sbin/installpkg: line 469: echo: write error: No space left on device
cat: write error: No space left on device
Installing package dynamix.cache.dirs-2015.04.28.txz:
PACKAGE DESCRIPTION:
/sbin/installpkg: line 537: echo: write error: No space left on device
/sbin/installpkg: line 538: echo: write error: No space left on device
/sbin/installpkg: line 539: echo: write error: No space left on device
/sbin/installpkg: line 540: echo: write error: No space left on device
/sbin/installpkg: line 545: echo: write error: No space left on device
/sbin/installpkg: line 550: echo: write error: No space left on device
/sbin/installpkg: line 559: echo: write error: No space left on device
WARNING: Package has not been created with 'makepkg'
Package dynamix.cache.dirs-2015.04.28.txz installed.


plugin: creating: /tmp/start_service - from INLINE content
plugin: running: 'anonymous'
chmod: missing operand after '644'
Try 'chmod --help' for more information.

-----------------------------------------------------------
Plugin dynamix.cache.dirs is installed.
This plugin requires Dynamix webGui to operate
Copyright 2015, Bergware International
Version: 2015.04.28
-----------------------------------------------------------

plugin: updated

 

 

Sometimes, because i also got updates that ran through without any error messages. Still running v6.14b, could this be the problem?

This has happened today for the updates to the following plugins: Community Repositories, Dynamix System Statistics, Dynamix System Temperature, Dynamix Cache Directories.

 

They all are working and are showing the latest version number. When i hit "Check for Updates" again, they all show as up-to-date.

I checked for free space on my unraid usb stick, but there is plenty. So dont really understand the "no space left on device" error message.

 

 

root@conchulio:~# df -h /boot
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda        3.8G  208M  3.6G   6% /boot

 

 

Wanted to check for something suspicious in the log but oddly the last log messages are from the 5th, so three days old and show these last lines:

 

May  5 23:28:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:29:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:30:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:31:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:32:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:33:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:34:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:35:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:36:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:37:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:38:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:39:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:40:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:41:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:42:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:43:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:44:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:45:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:46:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:47:16 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:48:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:49:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:50:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
May  5 23:51:01 conchulio crond[1486]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &>

 

 

What is going on here?

 

Full Syslog attached.

 

syslog2.zip

Shutdown the server and run chkdsk on your flash drive in a Windows machine. 

Will do that when i get a chance to. Not going to be at the server´s location for some days.

Thanks

Shutdown the server and run chkdsk on your flash drive in a Windows machine.

Shutting down the server will fix it, but this would probably fix the issue: http://lime-technology.com/forum/index.php?topic=39106.msg371313#msg371313

I had a chance to plug the usb-stick into my windows laptop and it came up as faulty.

Windows asked me if i want to check for and clear any errors, which i accepted.

It then did something, the progress bar was moving and the report after it finished showed zero errors.

 

When i un- and replugged the stick it was error free.

 

I just uprageded a few plugins on unRAID and there where no error messages.

 

So, thanks, and now i know what to do, if the error messages are coming back!

 

Should i think about getting a new usb-stick?

I had a chance to plug the usb-stick into my windows laptop and it came up as faulty.

Windows asked me if i want to check for and clear any errors, which i accepted.

It then did something, the progress bar was moving and the report after it finished showed zero errors.

 

When i un- and replugged the stick it was error free.

 

I just uprageded a few plugins on unRAID and there where no error messages.

 

So, thanks, and now i know what to do, if the error messages are coming back!

 

Should i think about getting a new usb-stick?

 

Do you have a UPS on this server?  Has the server been shutdown improperly lately?  (This usually results in a parity check at restart.)  The reason, I ask is if you have a UPS and then a parity check after restart, that would trend to indicated that the UPS battery ran out before the server completely shutdown.  If it was writing to an open file on the flash drive, that will create a file system error on the Flash drive. 

No, no UPS yet. But it's the next item on my shopping list.

I am not a hundred percent sure about the improper shutdown,but I am fairly certain that that's not the case. Otherwise I would have gotten an email notifying me about the parity check at the next array mount.