dlandon Posted March 3, 2017 Share Posted March 3, 2017 14 hours ago, Squid said: To see the current number of maximum watches: cat /proc/sys/fs/inotify/max_user_watches To change it: echo SomeNumber > /proc/sys/fs/inotify/max_user_watches Increasing the number of max watches has no effect on memory useage. Every watch utilized however does use a small amount of RAM This is probably from either Dynamix File integrity or Recycle Bin plugins The Recycle Bin plugin does not use inotifywait. File Activity plugin does. Link to comment
dlandon Posted March 3, 2017 Share Posted March 3, 2017 5 hours ago, Squid said: It all depends on your files. Mine's at 720000 with no problems. IIRC each file and each folder take a watch. The change isn't persistent though. You will either have to include that echo command in the "go" file (/boot/config/go) or as a user script starting at array start If you use the File Activity plugin, it allows you to change the max watches and it is persistent. Link to comment
trurl Posted March 3, 2017 Share Posted March 3, 2017 wrong csrf_token has been discussed many times on the forum. If you are getting it, then your sig must be wrong wrt your unRAID version. Link to comment
dmacias Posted March 3, 2017 Share Posted March 3, 2017 Just refresh your browser or close/reopen it to get rid of the csrf error. You could create a Temp folder in the config/plugins directory on your flash drive and move all the plg files there. You could also create a Temp folder in config/plugins/dynamix and move the plugin cron files there. I would even disable docker and vm's before you reboot Then reboot. You can close or refresh your browser but don't go back a page or you'll get the csrf error. See if there's any spam errors. If not, then reinstall the plugins one at time from the /config/plugins/Temp folder waiting and checking the log in between. Link to comment
jeffreywhunter Posted March 3, 2017 Author Share Posted March 3, 2017 5 hours ago, trurl said: wrong csrf_token has been discussed many times on the forum. If you are getting it, then your sig must be wrong wrt your unRAID version. Yep, it was wrong. On 6.3.2, all plugins updated to latest... Link to comment
jeffreywhunter Posted March 3, 2017 Author Share Posted March 3, 2017 4 hours ago, dmacias said: Just refresh your browser or close/reopen it to get rid of the csrf error. You could create a Temp folder in the config/plugins directory on your flash drive and move all the plg files there. You could also create a Temp folder in config/plugins/dynamix and move the plugin cron files there. I would even disable docker and vm's before you reboot Then reboot. You can close or refresh your browser but don't go back a page or you'll get the csrf error. See if there's any spam errors. If not, then reinstall the plugins one at time from the /config/plugins/Temp folder waiting and checking the log in between. Ugh, painful, but ok, will work through that... Link to comment
jeffreywhunter Posted May 26, 2017 Author Share Posted May 26, 2017 On 3/3/2017 at 0:50 PM, jeffreywhunter said: Ugh, painful, but ok, will work through that... @dmaciasFinally got around to trying this out. Doing all the things you said (plugins, dynamix), I'm still getting the same errors filling my log? I've upgraded to the latest Unraid 6.3.4. So weird... Thanks in advance for your thoughts... May 26 01:04:41 HunterNAS emhttp: Starting services... May 26 01:04:41 HunterNAS emhttp: nothing to sync May 26 01:05:01 HunterNAS crond[2348]: chdir failed: root Console and webGui login account May 26 01:05:01 HunterNAS crond[2347]: chdir failed: root Console and webGui login account May 26 01:05:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null May 26 01:05:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null May 26 01:06:01 HunterNAS crond[2611]: chdir failed: root Console and webGui login account May 26 01:06:01 HunterNAS crond[2612]: chdir failed: root Console and webGui login account May 26 01:06:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null May 26 01:06:16 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null May 26 01:07:01 HunterNAS crond[2875]: chdir failed: root Console and webGui login account May 26 01:07:01 HunterNAS crond[2876]: chdir failed: root Console and webGui login account May 26 01:07:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null May 26 01:07:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null May 26 01:08:01 HunterNAS crond[3139]: chdir failed: root Console and webGui login account May 26 01:08:01 HunterNAS crond[3140]: chdir failed: root Console and webGui login account May 26 01:08:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null May 26 01:08:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null May 26 01:09:01 HunterNAS crond[3403]: chdir failed: root Console and webGui login account May 26 01:09:01 HunterNAS crond[3404]: chdir failed: root Console and webGui login account May 26 01:09:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null May 26 01:09:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null May 26 01:10:01 HunterNAS crond[3740]: chdir failed: root Console and webGui login account May 26 01:10:01 HunterNAS crond[3741]: chdir failed: root Console and webGui login account May 26 01:10:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null May 26 01:10:16 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null May 26 01:11:01 HunterNAS crond[4005]: chdir failed: root Console and webGui login account May 26 01:11:01 HunterNAS crond[4006]: chdir failed: root Console and webGui login account May 26 01:11:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null May 26 01:11:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null hunternas-diagnostics-20170526-0111.zip Link to comment
jeffreywhunter Posted June 8, 2017 Author Share Posted June 8, 2017 On 3/2/2017 at 8:52 AM, Squid said: No. It just means that in safe mode, the plugin system is still adding in the cron entries for the various plugins, but since the plugins themselves aren't installed, the syslog is going to indicate errors everytime that particular cron entry runs. Explains why your /etc/cron.d/root file had the entries in safe mode, and why in safe mode you were still seeing the syslog spam from system stats (which runs every minute) Hey Squid, just wondering what came from your defect report on this. The server is usable at this point since none of the apps work. Should I try to reinstall everything from scratch? Link to comment
dmacias Posted June 8, 2017 Share Posted June 8, 2017 [mention=11874]dmacias[/mention]Finally got around to trying this out. Doing all the things you said (plugins, dynamix), I'm still getting the same errors filling my log? I've upgraded to the latest Unraid 6.3.4. So weird... Thanks in advance for your thoughts... May 26 01:04:41 HunterNAS emhttp: Starting services...May 26 01:04:41 HunterNAS emhttp: nothing to syncMay 26 01:05:01 HunterNAS crond[2348]: chdir failed: root Console and webGui login accountMay 26 01:05:01 HunterNAS crond[2347]: chdir failed: root Console and webGui login accountMay 26 01:05:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/nullMay 26 01:05:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/nullMay 26 01:06:01 HunterNAS crond[2611]: chdir failed: root Console and webGui login accountMay 26 01:06:01 HunterNAS crond[2612]: chdir failed: root Console and webGui login accountMay 26 01:06:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/nullMay 26 01:06:16 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/nullMay 26 01:07:01 HunterNAS crond[2875]: chdir failed: root Console and webGui login accountMay 26 01:07:01 HunterNAS crond[2876]: chdir failed: root Console and webGui login accountMay 26 01:07:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/nullMay 26 01:07:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/nullMay 26 01:08:01 HunterNAS crond[3139]: chdir failed: root Console and webGui login accountMay 26 01:08:01 HunterNAS crond[3140]: chdir failed: root Console and webGui login accountMay 26 01:08:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/nullMay 26 01:08:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/nullMay 26 01:09:01 HunterNAS crond[3403]: chdir failed: root Console and webGui login accountMay 26 01:09:01 HunterNAS crond[3404]: chdir failed: root Console and webGui login accountMay 26 01:09:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/nullMay 26 01:09:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/nullMay 26 01:10:01 HunterNAS crond[3740]: chdir failed: root Console and webGui login accountMay 26 01:10:01 HunterNAS crond[3741]: chdir failed: root Console and webGui login accountMay 26 01:10:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/nullMay 26 01:10:16 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/nullMay 26 01:11:01 HunterNAS crond[4005]: chdir failed: root Console and webGui login accountMay 26 01:11:01 HunterNAS crond[4006]: chdir failed: root Console and webGui login accountMay 26 01:11:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/nullMay 26 01:11:01 HunterNAS crond[1664]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null hunternas-diagnostics-20170526-0111.zipCheck your /config/passwd file on your flash drive. root should look like this.root:x:0:0:Console and webGui login account:/root:/bin/bash make sure you edit it with a linux friendly editor. Also maybe the dynamix local master or system stats could be the problem. Link to comment
jeffreywhunter Posted June 8, 2017 Author Share Posted June 8, 2017 4 hours ago, dmacias said: Check your /config/passwd file on your flash drive. root should look like this. root:x:0:0:Console and webGui login account:/root:/bin/bash make sure you edit it with a linux friendly editor. Also maybe the dynamix local master or system stats could be the problem. I have FTP activated (I'm accessing the server with my backup software via FTP since SMB isn't working very well.). There are a number of entries in that file and the one you mentioned "root" has the ftpuser added. Is that a problem? root:x:0:0:ftpuser Console and webGui login account:Console and webGui login account:/bin/bash bin:x:1:1:bin:/bin:/bin/false daemon:x:2:2:daemon:/sbin:/bin/false adm:x:3:4:adm:/var/log:/bin/false lp:x:4:7:lp:/var/spool/lpd:/bin/false mail:x:8:12:mail:/:/bin/false news:x:9:13:news:/usr/lib/news:/bin/false uucp:x:10:14:uucp:/var/spool/uucppublic:/bin/false ftp:x:14:50::/home/ftp:/bin/false smmsp:x:25:25:smmsp:/var/spool/clientmqueue:/bin/false mysql:x:27:27:MySQL:/var/lib/mysql:/bin/false rpc:x:32:32:RPC portmap user:/:/bin/false sshd:x:33:33:sshd:/:/bin/false gdm:x:42:42:GDM:/var/state/gdm:/bin/false avahi:x:61:214:Avahi Daemon User:/dev/null:/bin/false avahi-autoipd:x:62:62:Avahi AutoIP Daemon User:/dev/null:/bin/false messagebus:x:81:81::/dev/null:/bin/false pop:x:90:90:POP:/:/bin/false nobody:x:99:100:nobody:/:/bin/false jwh:x:1000:100:jwh:/:/bin/false ebh:x:1001:100::/:/bin/false ftpaccount:x:1002:100:ftpuser /mnt/user:/mnt/user/web:/bin/false proftpd-readme-important:x:1004:100:See flash/config/plugins/ProFTPd/readme for important info:/:/bin/false Link to comment
Squid Posted June 8, 2017 Share Posted June 8, 2017 12 hours ago, jeffreywhunter said: Hey Squid, just wondering what came from your defect report on this. The server is usable at this point since none of the apps work. Should I try to reinstall everything from scratch? According to the changelogs, fix went in with 6.3.3 Quote update_cron: generate system cron table only from installed plugins Link to comment
dmacias Posted June 8, 2017 Share Posted June 8, 2017 I have FTP activated (I'm accessing the server with my backup software via FTP since SMB isn't working very well.). There are a number of entries in that file and the one you mentioned "root" has the ftpuser added. Is that a problem?root:x:0:0:ftpuser Console and webGui login account:Console and webGui login account:/bin/bashbin:x:1:1:bin:/bin:/bin/falsedaemon:x:2:2:daemon:/sbin:/bin/falseadm:x:3:4:adm:/var/log:/bin/falselp:x:4:7:lp:/var/spool/lpd:/bin/falsemail:x:8:12:mail:/:/bin/falsenews:x:9:13:news:/usr/lib/news:/bin/falseuucp:x:10:14:uucp:/var/spool/uucppublic:/bin/falseftp:x:14:50::/home/ftp:/bin/falsesmmsp:x:25:25:smmsp:/var/spool/clientmqueue:/bin/falsemysql:x:27:27:MySQL:/var/lib/mysql:/bin/falserpc:x:32:32:RPC portmap user:/:/bin/falsesshd:x:33:33:sshd:/:/bin/falsegdm:x:42:42:GDM:/var/state/gdm:/bin/falseavahi:x:61:214:Avahi Daemon User:/dev/null:/bin/falseavahi-autoipd:x:62:62:Avahi AutoIP Daemon User:/dev/null:/bin/falsemessagebus:x:81:81::/dev/null:/bin/falsepop:x:90:90:POP:/:/bin/falsenobody:x:99:100:nobody:/:/bin/falsejwh:x:1000:100:jwh:/:/bin/falseebh:x:1001:100::/bin/falseftpaccount:x:1002:100:ftpuser /mnt/user:/mnt/user/web:/bin/falseproftpd-readme-important:x:1004:100:See flash/config/plugins/ProFTPd/readme for important info:/:/bin/false Yes that's the problem.The format should look like the example I posted e.g.root:x:0:0:description:home_path: shellroot:x:0:0:Console and webGui login account:/root:/bin/bashSo yours has home directory or path set to "Console and webGui login account" it should be /root. Change it to match. Every root command was probably giving errors because of this. Link to comment
jeffreywhunter Posted June 8, 2017 Author Share Posted June 8, 2017 1 hour ago, dmacias said: Yes that's the problem. The format should look like the example I posted e.g. root:x:0:0:description:home_path: shell root:x:0:0:Console and webGui login account:/root:/bin/bash So yours has home directory or path set to "Console and webGui login account" it should be /root. Change it to match. Every root command was probably giving errors because of this. What would have changed this? I made the changes you suggested, and it changed the way things operate. However, now I'm getting a different repeating message: which I think is because I've deleted all the various plugins. Will try to fix that next... Tail of syslog - full log attached. Jun 8 13:35:48 HunterNAS emhttp: shcmd (80): sync Jun 8 13:35:49 HunterNAS emhttp: shcmd (81): mkdir /mnt/user0 Jun 8 13:35:49 HunterNAS emhttp: shcmd (82): /usr/local/sbin/shfs /mnt/user0 -disks 2046 -o noatime,big_writes,allow_other |& logger Jun 8 13:35:49 HunterNAS emhttp: shcmd (83): mkdir /mnt/user Jun 8 13:35:49 HunterNAS emhttp: shcmd (84): /usr/local/sbin/shfs /mnt/user -disks 2047 2048000000 -o noatime,big_writes,allow_other -o remember=330 |& logger Jun 8 13:35:49 HunterNAS emhttp: shcmd (85): cat - > /boot/config/plugins/dynamix/mover.cron <<< "# Generated mover schedule:#0120 */3 * * * /usr/local/sbin/mover |& logger#012" Jun 8 13:35:49 HunterNAS emhttp: shcmd (86): /usr/local/sbin/update_cron &> /dev/null Jun 8 13:35:49 HunterNAS emhttp: Starting services... Jun 8 13:35:49 HunterNAS emhttp: nothing to sync Jun 8 13:36:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:36:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:37:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:37:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:38:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:38:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:39:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:39:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:40:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:40:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:41:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:41:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:42:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:42:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:43:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:43:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:44:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:44:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:45:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:45:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:46:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:46:16 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:47:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:47:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:48:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:48:16 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:49:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:49:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Jun 8 13:50:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null Jun 8 13:50:01 HunterNAS crond[1663]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null hunternas-diagnostics-20170608-1352.zip Link to comment
dmacias Posted June 8, 2017 Share Posted June 8, 2017 I would guess either a glitch in a ftp plugin and it was trying to create a ftp user. Or it could have been some sort of flash drive corruption. Reinstall the dynamix local master and system stats or put your flash drive back like it was. Link to comment
truetype Posted November 25, 2018 Share Posted November 25, 2018 @jeffreywhunter Old post I know, but did you find a solution to this? My log is getting spammed by this too.. Nov 25 12:15:01 unTRUE crond[14638]: chdir failed: root Console and webGui login account Nov 25 12:15:01 unTRUE crond[14639]: chdir failed: root Console and webGui login account Nov 25 12:15:01 unTRUE crond[14640]: chdir failed: root Console and webGui login account Nov 25 12:16:01 unTRUE crond[17298]: chdir failed: root Console and webGui login account Nov 25 12:16:01 unTRUE crond[17300]: chdir failed: root Console and webGui login account Nov 25 12:16:01 unTRUE crond[17301]: chdir failed: root Console and webGui login account Nov 25 12:17:01 unTRUE crond[20049]: chdir failed: root Console and webGui login account Nov 25 12:17:01 unTRUE crond[20050]: chdir failed: root Console and webGui login account Nov 25 12:17:01 unTRUE crond[20051]: chdir failed: root Console and webGui login account Nov 25 12:18:01 unTRUE crond[22664]: chdir failed: root Console and webGui login account Nov 25 12:18:01 unTRUE crond[22665]: chdir failed: root Console and webGui login account Nov 25 12:18:01 unTRUE crond[22666]: chdir failed: root Console and webGui login account Nov 25 12:19:01 unTRUE crond[25663]: chdir failed: root Console and webGui login account Nov 25 12:19:01 unTRUE crond[25662]: chdir failed: root Console and webGui login account Nov 25 12:19:01 unTRUE crond[25664]: chdir failed: root Console and webGui login account Nov 25 12:20:01 unTRUE crond[28354]: chdir failed: root Console and webGui login account Nov 25 12:20:01 unTRUE crond[28355]: chdir failed: root Console and webGui login account Nov 25 12:20:01 unTRUE crond[28356]: chdir failed: root Console and webGui login account Nov 25 12:21:01 unTRUE crond[31035]: chdir failed: root Console and webGui login account Nov 25 12:21:01 unTRUE crond[31036]: chdir failed: root Console and webGui login account Nov 25 12:21:01 unTRUE crond[31037]: chdir failed: root Console and webGui login account Nov 25 12:22:01 unTRUE crond[1232]: chdir failed: root Console and webGui login account Nov 25 12:22:01 unTRUE crond[1233]: chdir failed: root Console and webGui login account Nov 25 12:22:01 unTRUE crond[1234]: chdir failed: root Console and webGui login account Nov 25 12:23:01 unTRUE crond[3875]: chdir failed: root Console and webGui login account Nov 25 12:23:01 unTRUE crond[3876]: chdir failed: root Console and webGui login account Nov 25 12:23:01 unTRUE crond[3877]: chdir failed: root Console and webGui login account Nov 25 12:24:01 unTRUE crond[7185]: chdir failed: root Console and webGui login account Nov 25 12:24:01 unTRUE crond[7184]: chdir failed: root Console and webGui login account Nov 25 12:24:01 unTRUE crond[7186]: chdir failed: root Console and webGui login account Nov 25 12:25:01 unTRUE crond[10399]: chdir failed: root Console and webGui login account Nov 25 12:25:01 unTRUE crond[10400]: chdir failed: root Console and webGui login account Nov 25 12:25:01 unTRUE crond[10401]: chdir failed: root Console and webGui login account Nov 25 12:26:01 unTRUE crond[14521]: chdir failed: root Console and webGui login account Nov 25 12:26:01 unTRUE crond[14522]: chdir failed: root Console and webGui login account Nov 25 12:26:01 unTRUE crond[14523]: chdir failed: root Console and webGui login account Nov 25 12:27:01 unTRUE crond[17738]: chdir failed: root Console and webGui login account Nov 25 12:27:01 unTRUE crond[17739]: chdir failed: root Console and webGui login account Nov 25 12:27:01 unTRUE crond[17740]: chdir failed: root Console and webGui login account Link to comment
Squid Posted November 25, 2018 Share Posted November 25, 2018 2 hours ago, truetype said: @jeffreywhunter Old post I know, but did you find a solution to this? My log is getting spammed by this too.. You would have to post the output of crontab -l cat /etc/cron.d/root Link to comment
truetype Posted November 25, 2018 Share Posted November 25, 2018 4 minutes ago, Squid said: You would have to post the output of crontab -l cat /etc/cron.d/root Thanks. This is what I get: login as: root root@untrue's password: Last login: Sun Nov 25 14:58:23 2018 from 192.168.1.5 Linux 4.18.17-unRAID. Could not chdir to home directory Console and webGui login account: No such file or directory -bash: [: too many arguments root@unTRUE:/# clear root@unTRUE:/# crontab -l # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null 0 3 2 * * /usr/local/emhttp/plugins/ca.backup2/scripts/backup.php &>/dev/null 2>&1 root@unTRUE:/# root@unTRUE:/# root@unTRUE:/# cat /etc/cron.d/root # Generated docker monitoring schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 0 1 * * * /usr/local/sbin/mover &> /dev/null # Generated parity check schedule: 0 2 * * 1 /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated system data collection schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null # Purge recycle bin at 3:00 on the first day of the week: 0 3 * * 0 /usr/local/emhttp/plugins/recycle.bin/scripts/rc.recycle.bin cron &> /dev/null root@unTRUE:/# Link to comment
Squid Posted November 25, 2018 Share Posted November 25, 2018 3 minutes ago, truetype said: login as: root root@untrue's password: Last login: Sun Nov 25 14:58:23 2018 from 192.168.1.5 Linux 4.18.17-unRAID. Could not chdir to home directory Console and webGui login account: No such file or directory -bash: [: too many arguments This is the key, and you should not be seeing any message like that ever when logging in. Restart the system in safe mode and does that error disappear? And does it re-appear when you reboot again normally? Link to comment
truetype Posted November 25, 2018 Share Posted November 25, 2018 17 minutes ago, Squid said: This is the key, and you should not be seeing any message like that ever when logging in. Restart the system in safe mode and does that error disappear? And does it re-appear when you reboot again normally? Hmm okey thats sounds wierd.. I tried booting in safe mode with gui (no plugins) but the warning still appeared every minute. Booted up normally now and no change. Link to comment
truetype Posted November 25, 2018 Share Posted November 25, 2018 3 minutes ago, Squid said: post the diagnostics Here, sorry, should've understood I should've done that immediately. untrue-diagnostics-20181125-1530.zip Link to comment
John_M Posted November 25, 2018 Share Posted November 25, 2018 Check your passwd file, like here: Link to comment
truetype Posted November 25, 2018 Share Posted November 25, 2018 2 minutes ago, John_M said: Check your passwd file, like here: This sounds like it's related now when you are mentioning it. A while back I tried adding "ftpuser" in root's user comment in order to use it for FTP in last unraid version when the SFTP was bugged. Maybe this didn't reverse correctly. Link to comment
John_M Posted November 25, 2018 Share Posted November 25, 2018 That was the root cause of the OP's problem. The entry had got corrupted. The rest was because he'd deactivated plugins in his attempts to troubleshoot. The system is trying to access the root user's home directory but it's incorrectly set in the passwd file. Link to comment
truetype Posted November 25, 2018 Share Posted November 25, 2018 11 minutes ago, John_M said: That was the root cause of the OP's problem. The entry had got corrupted. The rest was because he'd deactivated plugins in his attempts to troubleshoot. The system is trying to access the root user's home directory but it's incorrectly set in the passwd file. Thanks this made the warning stop spamming every minute! Though now I got the "csrf_token" error and "broken_pipe" error mentioned above. They just appeared once though, they are not spamming. And when I look at the unraid screen (not webgui) I see above the login prompt "cat: write error: Broken pipe" Nov 25 15:47:27 unTRUE avahi-daemon[9908]: Service "unTRUE" (/services/sftp-ssh.service) successfully established. Nov 25 15:47:28 unTRUE root: error: /webGui/include/Boot.php: wrong csrf_token Nov 25 15:47:32 unTRUE unassigned.devices: Mounting 'Auto Mount' Devices... Nov 25 15:47:32 unTRUE unassigned.devices: Disk with serial 'Samsung_SSD_850_EVO_500GB_S21JNXAG642834Z', mountpoint 'Samsung_SSD_850_EVO_500GB_S21JNXAG642834Z' is not set to auto mount and will not be mounted... Nov 25 15:47:32 unTRUE emhttpd: Starting services... Nov 25 15:47:32 unTRUE emhttpd: shcmd (73): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 40 Nov 25 15:47:32 unTRUE kernel: BTRFS: device fsid 506f329d-2300-4cf7-ae52-123ef0099a09 devid 1 transid 1508808 /dev/loop2 Nov 25 15:47:32 unTRUE kernel: BTRFS info (device loop2): disk space caching is enabled Nov 25 15:47:32 unTRUE kernel: BTRFS info (device loop2): has skinny extents Nov 25 15:47:33 unTRUE root: Resize '/var/lib/docker' of 'max' Nov 25 15:47:33 unTRUE kernel: BTRFS info (device loop2): new size for /dev/loop2 is 42949672960 Nov 25 15:47:33 unTRUE emhttpd: shcmd (75): /etc/rc.d/rc.docker start Nov 25 15:47:33 unTRUE root: starting dockerd ... Nov 25 15:47:42 unTRUE avahi-daemon[9908]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Nov 25 15:47:42 unTRUE avahi-daemon[9908]: New relevant interface docker0.IPv4 for mDNS. Nov 25 15:47:42 unTRUE avahi-daemon[9908]: Registering new address record for 172.17.0.1 on docker0.IPv4. Nov 25 15:47:42 unTRUE kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready Nov 25 15:47:50 unTRUE root: Starting docker_load Nov 25 15:47:50 unTRUE emhttpd: shcmd (89): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 Nov 25 15:47:50 unTRUE kernel: BTRFS: device fsid 5c55a16f-04c0-45e1-89c4-8e4234b5e760 devid 1 transid 549 /dev/loop3 Nov 25 15:47:50 unTRUE kernel: BTRFS info (device loop3): disk space caching is enabled Nov 25 15:47:50 unTRUE kernel: BTRFS info (device loop3): has skinny extents Nov 25 15:47:50 unTRUE root: Resize '/etc/libvirt' of 'max' Nov 25 15:47:50 unTRUE kernel: BTRFS info (device loop3): new size for /dev/loop3 is 1073741824 Nov 25 15:47:50 unTRUE emhttpd: shcmd (91): /etc/rc.d/rc.libvirt start Nov 25 15:47:50 unTRUE root: Starting virtlockd... Nov 25 15:47:50 unTRUE root: Starting virtlogd... Nov 25 15:47:50 unTRUE root: Starting libvirtd... Nov 25 15:47:50 unTRUE kernel: tun: Universal TUN/TAP device driver, 1.6 Nov 25 15:47:50 unTRUE emhttpd: nothing to sync Nov 25 15:47:50 unTRUE emhttpd: error: send_file, 139: Broken pipe (32): sendfile: /usr/local/emhttp/logging.htm Nov 25 15:47:50 unTRUE kernel: docker0: port 1(veth229fdcb) entered blocking state Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.