Jump to content

dlandon

Community Developer
  • Posts

    10,398
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by dlandon

  1. For consistency with the array file permissions, the 'create 0644 nobody users' should be changed to 'create 0666 nobody users'. This sets permissions to -rw-rw-rw-.
  2. The mover does not run at times and errors out. Feb 24 04:40:48 MediaServer crond[1767]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null From the mover script, this error is from the mover supposedly already running. start() { if [ -f $PIDFILE ]; then if ps h $(cat $PIDFILE) | grep mover ; then echo "mover: already running" exit 1 fi fi According to the log, the mover is not running. This is the contents of /var/run/. There is no mover.pid. -rw-r--r-- 1 root root 5 Feb 23 06:11 acpid.pid srw-rw-rw- 1 root root 0 Feb 23 06:11 acpid.socket= -rw-r--r-- 1 root root 6 Feb 24 04:40 apcupsd.pid -rw-r--r-- 1 root root 5 Feb 23 06:11 atd.pid drwxr-xr-x 2 root root 80 Feb 23 06:11 dbus/ drwx------ 6 root root 140 Feb 23 06:12 docker/ srw-rw---- 1 root docker 0 Feb 23 06:12 docker.sock= -rw-r--r-- 1 root root 4 Feb 23 06:12 dockerd.pid srw-rw-rw- 1 root root 0 Feb 23 06:11 emhttpd.socket= -rw-rw-rw- 1 root root 4 Feb 23 06:11 haveged.pid -rw-rw-rw- 1 root root 5 Feb 23 06:12 inetd.pid drwxr-xr-x 8 root root 360 Feb 23 06:12 libvirt/ -rw-rw-rw- 1 root root 24 Feb 23 06:12 nginx.origin -rw-r--r-- 1 root root 5 Feb 23 06:12 nginx.pid srw-rw-rw- 1 root root 0 Feb 23 06:12 nginx.socket= -rw-r--r-- 1 root root 5 Feb 23 06:12 nmbd.pid drwxr-xr-x 2 root root 40 Aug 3 2018 nscd/ -rw-r--r-- 1 root root 4 Feb 23 06:11 ntpd.pid -rw-r--r-- 1 root root 4 Feb 23 06:12 php-fpm.pid srw-rw---- 1 root users 0 Feb 23 06:12 php5-fpm.sock= drwxr-xr-x 2 root root 60 Feb 24 06:37 recycle.bin/ -rw-rw-rw- 1 rpc rpc 5 Feb 23 06:11 rpc.statd.pid drwxr-xr-x 2 rpc root 40 Nov 15 13:00 rpcbind/ -r--r--r-- 1 root root 0 Feb 23 06:11 rpcbind.lock srw-rw-rw- 1 root root 0 Feb 23 06:11 rpcbind.sock= -rw-r--r-- 1 root root 4 Feb 23 06:12 rsyslogd.pid -rw-r--r-- 1 root root 1 Feb 23 06:11 runlevel drwxr-xr-x 5 root root 100 Feb 23 06:11 samba/ -rw------- 1 root root 5 Feb 23 06:11 sm-notify.pid -rw-r--r-- 1 root root 5 Feb 23 06:12 smbd.pid -rw-r--r-- 1 root root 5 Feb 23 06:12 sshd.pid -rw-r--r-- 1 root root 4 Feb 23 06:12 syslogd.pid srwxrwxrwx 1 root root 0 Feb 23 06:12 ttyd.sock= -rw-rw-r-- 1 root utmp 4608 Feb 24 06:35 utmp -rw-r--r-- 1 root root 5 Feb 23 06:12 winbindd.pid Contents of /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: 40 3 * * * /usr/local/sbin/mover &> /dev/null # Generated parity check schedule: 0 9 1 * * /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null || : # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated array status check schedule: 20 0 * * * /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null # Generated Unraid OS update check schedule: 11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null # Generated local master browser check: */1 * * * * /usr/local/emhttp/plugins/dynamix.local.master/scripts/localmaster &> /dev/null # Generated ssd trim schedule: 30 5 * * * /sbin/fstrim -a -v | logger &> /dev/null # Purge recycle bin at 3:00 every day: 0 3 * * * /usr/local/emhttp/plugins/recycle.bin/scripts/rc.recycle.bin cron &> /dev/null # Refresh Recycle Bin trash sizes every minute: * * * * * /usr/local/emhttp/plugins/recycle.bin/scripts/get_trashsizes &> /dev/null 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 The mover then does not run and files are left on the cache. I'm pretty sure that there aren't any plugins interfering with the mover cron. mediaserver-diagnostics-20190224-1122.zip
  3. Because if all the file writing, it is suggested it be on the cache because it will keep hard drives spun up. Actually a better reference would be '/mnt/user/syslog'. It works no matter where the syslog share is located.
  4. Rotated Unraid syslogs do the same thing. Quite nice. Thanks @bonienl for the syslog server feature,
  5. Got it. Should it also have 'missingok'? I have a script in User Scripts that runs on first array start that copies the file along with a few other startup things.
  6. Would it also work to create a file with these settings and copy it to the /etc/logrotate.d/ folder? Seems a little cleaner to copy the file on system start and not have to edit the logrotate.conf file.
  7. IInstall the Unassigned Disks plugin and the disk should spin down.
  8. It appears that what I was trying to do with the cleaning out the log file is not allowed with rsyslog. It is similar to rotating the log file. Ryslog has to close the file and then restart after the file is rotated, or changed as in my case. I'm just going to collect the raw output from my router and download it and clean it if necessary to review it. This begs the question though of how does a person rotate, or trim down the size of the log file. I could see it getting quite large if not managed. Maybe a logrotate needs to be set up for the remote log files to keep them cut down in size.
  9. I think I have figured it out. The log that I was having trouble with was from my router. It logs a lot of extraneous stuff that I was trying to remove on the Unraid side. I set up a script to run every hour to remove the extraneous stuff. Apparently the Syslog Server is confused by this and stops adding to the file. I assumed the Syslog Server just appended the latest log entries, but I'm not sure it does that. I turned off the log cleaning script and I'll see if it stops again.
  10. -rw-rw-rw- 1 nobody users 20265 Feb 22 20:10 syslog-192.168.1.1.log -rw-rw-rw- 1 nobody users 1 Feb 22 06:35 syslog-192.168.1.2.log -rw-rw-rw- 1 nobody users 748430 Feb 22 20:15 syslog-192.168.1.3.log -rw-rw-rw- 1 nobody users 3136546 Feb 22 19:20 syslog-192.168.1.4.log I changed the permissions to -rw-rw-rw- to be consistent with Unraid permissions. Nothing strange in the sizes. I suspect an issue with the router. I haven't had any issues with any other devices.
  11. Is there a Syslog Server log? My router stops logging at after some time and I have stop and restart the Syslog Server on Unraid to get it working again.
  12. Yes. The latest qemu guest agent for 32 bit complains that it won't install on a 64 bit machine.
  13. Manually added the balloon device to the xml and got the driver working, but still the same issue with the 64 bit qemu driver. I always thought it was the serial driver that was needed for the guest agent. It makes sense. This is what I always do on Windows VMs. I just may have to stick with an older 32 bit guest agent and not worry about it.
  14. If this is true, then I have a conundrum. I pass through a pci GPU to that VM and according to the VM editor help: If you are passing through a PCI device, only the initial memory value is used and the max memory value is ignored. Not only does that apply, but the editor disables the balloon device: <memballoon model='none'/> So I can't pass through a pci device and install the newer 64 bit qemu guest agent because there is no balloon device? Seems like a bit of a conflict.
  15. Thanks. I'll take a look at the new drivers. I fixed the scsi error. I hadn't changed my xml with the editor in a long time and apparently messed things up with some manual editing. Changing things with the editor straightened things out.
  16. So, back to the original reason for posting. How do I get past the qemu 64 bit install problem? The newer drivers insist on a 64 bit install, but it doesn't work so I have to go back to older drivers and install the 32 bit version.
  17. You won't be able to shutdown or hibernate the VM from the VM menu. Correct. I believe shutdown of the VM will also not work.
  18. The 'Bar (gray) - Text' and 'Bar (color) - Text' both show as Text - Bar.
  19. Gotta love troubleshooting other people's sloppy work.
  20. The best I can tell, you were copying to a UD remote mounted share. I don't know your network configuration, but the log shows some network issues. Feb 21 15:53:41 Omega kernel: mlx4_en: eth4: Link Down Feb 21 15:53:41 Omega kernel: br4: port 1(eth4) entered disabled state Feb 21 15:54:33 Omega kernel: mlx4_en: eth4: Link Up Feb 21 15:54:33 Omega kernel: br4: port 1(eth4) entered blocking state Feb 21 15:54:33 Omega kernel: br4: port 1(eth4) entered forwarding state Feb 21 15:54:33 Omega kernel: mlx4_en: eth4: Link Down Feb 21 15:54:33 Omega kernel: mlx4_en: eth4: Link Up Feb 21 15:54:38 Omega kernel: CIFS VFS: BAD_NETWORK_NAME: \\192.168.10.4\personal Feb 21 15:54:38 Omega kernel: reconnect tcon failed rc = -2 Feb 21 15:54:40 Omega kernel: CIFS VFS: BAD_NETWORK_NAME: \\192.168.10.4\personal Feb 21 15:54:42 Omega kernel: CIFS VFS: BAD_NETWORK_NAME: \\192.168.10.4\personal Feb 21 15:54:44 Omega kernel: CIFS VFS: BAD_NETWORK_NAME: \\192.168.10.4\personal Feb 21 15:54:46 Omega kernel: CIFS VFS: BAD_NETWORK_NAME: \\192.168.10.4\personal Feb 21 15:54:48 Omega kernel: CIFS VFS: BAD_NETWORK_NAME: \\192.168.10.4\personal Unless you have a need to log the mover, you should disable it. It floods your log with mover actions. You should also review your log and see what you need to do to clear up some other issues. Feb 21 16:11:57 Omega rpcbind[6974]: connect from 192.168.10.30 to getport/addr(mountd) Feb 21 16:11:57 Omega rpcbind[6975]: connect from 192.168.10.30 to getport/addr(mountd) Feb 21 16:11:57 Omega rpcbind[6976]: connect from 192.168.10.30 to getport/addr(mountd) Feb 21 16:11:57 Omega rpcbind[6978]: connect from 192.168.10.30 to getport/addr(mountd) Feb 21 16:12:00 Omega rpcbind[7116]: connect from 192.168.10.30 to null() Feb 21 16:12:00 Omega rpcbind[7117]: connect from 192.168.10.30 to getport/addr(mountd) Feb 21 16:12:00 Omega rpcbind[7118]: connect from 192.168.10.30 to null() eb 20 17:16:35 Omega root: Fix Common Problems Version 2019.02.18 Feb 20 17:16:35 Omega root: Fix Common Problems: Warning: Share isos set to not use the cache, but files / folders exist on the cache drive Feb 20 17:16:36 Omega root: Fix Common Problems: Warning: Deprecated plugin fix.common.problems.plg Feb 20 17:16:39 Omega root: Fix Common Problems: Other Warning: CPU possibly will not throttle down frequency at idle Feb 20 17:16:40 Omega root: Fix Common Problems: Other Warning: Mover logging is enabled ** Ignored
×
×
  • Create New...