dlandon

Instead of using 'Load Shares', just enter the name of the share manually.

Where is it that you don't see the NFS shares? From the UD gui, click on the 'Add Remote SMB/NFS Share', select the 'NFS' protocol, then fill in the 'Host/IP' address of the remote server and the 'Share'. You should be able to mount it then.

When you can do it, go to the command line and run this command rather than using the web ui so it doesn't hang if there is a problem: /usr/local/emhttp/plugins/recycle.bin/scripts/rc.recycle.bin stop It should only take a few seconds to return. When I asked about your system being busy, I really meant the amount of disk activity. The recycle bin trash size has to hit the disks to determine the sizes of the .Recycle.Bin folders and if there is a lot of disk activity it can take a while. With the recent update, I've moved all trash size checks to the background in case any of this was hanging the UI. The downside is the trash sizes may show '?' if the trash size check times out, but I guess this is better than a hung up UI. That large rsync copy could slow down the recycle bin trash size check.

If you still have the issue after updating the recycle bin, let me know. Is your server real busy?

Update the recycle bin plugin and then see if it helps. I found a case where the web ui could take a while to respond. I now update the trash sizes in the background in all cases so the web ui can stay responsive.

This is just stopping the recycle bin and not doing a shut down?

As a test I changed this to see if it was where the error occurred: start() { if [ -f $PIDFILE ]; then if ps h $(cat $PIDFILE) | grep mover ; then echo "mover: already running" exit 10 fi fi I got the same error: Feb 27 03:45:56 BackupServer crond[1675]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null I think bonienl is right. The error is occurring later in the script and occurs when the logging is turned off. That's why turning on logging does not create this error.

diagnostics

If it hangs again and you can get to the command line, capture diagnostics.

Make sure all your plugins are up to date.

The 9000 port change you made is for the WebUI and is only part of the change needed to remap LMS. I am not an expert at this because I use the default port setup, but there is also a 'Web Server Port Number' in LMS settings that is set to 9000 which I believe is the port the players use to stream the music. I think this is in conflict with your other 9000 port. You could remap this, but then the Docker xml would have to be edited to let your new port pass through to LMS. You'd probably have to set the LMS Docker to a static IP address and change the network type to 'Host' to open up all the ports to LMS.

I don't think it's your shares. I think it's your port mapping. Remove the port conflict for a test and install LMS with the defaults and see if it works.

Those are both on the disks_mounted event. The recycle bin should not take that long. There may be a lot of other things loading on the disks_mounted event and could be slowing things down between the recycle bin and UD, along with the normal start up stuff. Here is a snippet from my log. There is not that much time between the events. Feb 25 19:28:52 MediaServer Recycle Bin: Starting Recycle Bin Feb 25 19:28:52 MediaServer emhttpd: Starting Recycle Bin... Feb 25 19:28:52 MediaServer rsyslogd: [origin software="rsyslogd" swVersion="8.40.0" x-pid="4941" x-info="https://www.rsyslog.com"] start Feb 25 19:28:53 MediaServer ntpd[1692]: Listen normally on 5 br0 192.168.1.3:123 Feb 25 19:28:53 MediaServer ntpd[1692]: Listen normally on 6 br0 [2605:a000:1317:86ba::1282]:123 Feb 25 19:28:53 MediaServer ntpd[1692]: Listen normally on 7 br0 [fe80::acbb:b8ff:fef8:5623%13]:123 Feb 25 19:28:53 MediaServer ntpd[1692]: new interface(s) found: waking up resolver Feb 25 19:29:13 MediaServer unassigned.devices: Mounting 'Auto Mount' Devices... It looks like some network stuff is happening in my case. Post your diagnostics and I'll have a look.

Been there and done that. rc.diskinfo is a preclear script. The lsof command is from preclear. Glad you solved it.

Ok. It seems I did have an issue like this. I changed the rule and we'll see how it works. I'm extremely grateful for the syslog server capability and now with being able to filter a large number of extraneous messages from the router log, I can finally read it. I can't scroll back in the log on the router because it refreshes a lot and starts all over at the top when it does. I really like the idea of keeping server logs in a more permanent place and current in case of an unplanned shutdown. Thanks @ljm42 for all your help here.

It looks to be from the preclear plugin. Remove it and see if it makes a difference.

You haven't provided enough information for anyone to help you. What is the device used for? Post diagnostics so we can take a look.

I've set it up as you suggested, but it is not working for me yet. I'll wait for the next release with the fixes.

Do these rules apply to all logs? I Want to filter some messages from my router. It is flooded with extraneous messages.

Stop the recycle bin, then try to stop the server. I don't think the recycle bin is hanging, it's probably the last message displayed before it hangs.

I was referring to the log file permissions in the syslog share, not the logrotate file permission. missingok create 0666 nobody users size 1M All files written to the array shares are set to 666 permissions. If you do a Tools->New Permissions, the file permissions will be set to: For read/write files: -rw-rw-rw-

I would. If you have the User Scripts plugin installed, it would be cleaner to set it up there to copy on first array start. Editing the 'go' file these days is highly discouraged.

I've tried to turn on mover logging to catch this error, but I have not been able to catch it.

The way I read the script it didn't get that far. I agree. This is not just a situation of the exit code from the mover or the start/stop showing in the log. I have logging turned off, so I get it that the mover started/stopped messages won't show in the log. Regardless, the mover failed to run.