yp_1

As of now I have the backup against an SMB share (created using the above script) working on Sonoma. No issues.

Also, you will need to give cron Full Disk Access for the cron entry created by the above script to work: https://osxdaily.com/2020/04/27/fix-cron-permissions-macos-full-disk-access/

tmbackup.sh The above script is based on https://community.jamf.com/t5/jamf-pro/scripts-for-timemachine-backups-over-smb-with-automounting-on/td-p/277978 It has to be run only once, as a regular user, but will ask for password for commands that require sudo, so make sure the user has Admin privileges set. Basically it will set up autofs to mount the SMB share and respective sparsebundle. Obviously, modify the script if required.

I stand corrected. This is not a solution.

You can specify alternative port: https://sleeplessbeastie.eu/2020/09/14/how-to-specify-custom-ssh-port-when-using-rdiff-backup/ I am going to try setting up a container since I need this too.

I've set it up using Community Applications plugin. It is running and listens on port 3689, but it does not seem to announce itself, so I can't see it in iTunes. Unlike Firefly server. What do I do to fix that?

Below is my workaround. Leave the settings in the gui as they are. Replace /mnt/user/plugins/Plexmediaserver with your own path if you wish. mkdir -p /mnt/user/plugins/Plexmediaserver/tmp chmod 1777 /mnt/user/plugins/Plexmediaserver/tmp cp -Rp /usr/local/Plexmediaserver/config /mnt/user/plugins/Plexmediaserver cat >>/boot/config/go <<EOF [ -d /usr/local/Plexmediaserver ] || mkdir /usr/local/Plexmediaserver ln -s /mnt/user/plugins/Plexmediaserver/config /usr/local/Plexmediaserver [ -d /tmp/Plexmediaserver ] && rmdir /tmp/Plexmediaserver ln -s /mnt/user/plugins/Plexmediaserver/tmp /tmp/Plexmediaserver EOF Hope this helps.

Yes, I only use NFS, no Samba or AFP here. I've not experience any problems. What were the circumstances which provoked this error? A quick google suggests that the textual description of 107 is 'peername failed'. I'm not quite sure what that means in terms of nfs. Sorry, I replied quoted wrong message. Here it is again. I can't reproduce the error anymore. But there are 5 nfsd threads running in interruptible state (D) blocking IO and causing LAVG of 12 on my dual core system. Definitely a problem. I don't run anything special on NFS - just backup my ESX VMs by copying their snapshot to a NFS mounted datastore. The problem never existed before and I assume it is specific to the newer kernel. Since ther is nothing in the logs at this point I don't know what else can be done to determine a problem. root@Tower:/var/log# ps ax|grep nfsd|grep D 10387 ? D 0:24 [nfsd] 10388 ? D 0:24 [nfsd] 10390 ? D 0:24 [nfsd] 10392 ? D 0:25 [nfsd] 10393 ? D 0:23 [nfsd] 10394 ? D 0:25 [nfsd] root@Tower:/var/log# vmstat 2 procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu---- r b swpd free buff cache si so bi bo in cs us sy id wa 0 5 0 131088 92516 3631040 0 0 13 1461 888 1038 0 4 7 89 0 5 0 131080 92516 3631040 0 0 0 0 205 66 0 0 0 100 0 5 0 131080 92516 3631040 0 0 0 0 206 64 0 0 0 100

Is somebody using NFS with this release? I upgraded and NFS seems to be broken (saw something like nfsd unknown error -107 in syslog). RC5 works fine.

Here is the link: http://www.supermicro.com/about/policies/disclaimer.cfm?url=/manuals/other/AMI_BIOS_Recovery.pdf They emailed me RMA form today. Just email [email protected].

Same here And exactly the same sequence. Emailed Supermicro, received the recovery instructions but none of them worked, including serial port recovery. Will see if they honor the warranty and flash it. Meantime I have to buy a new board. And this time it won't be Supermicro...

Since I upgraded from 4.7 my server locks up during backup of a few VMs on my ESXi NFS store epxorted from the unraid server. It happened now 2 times in a row. The backup job runs nightly and I have been using same setup (ghettobackup2.pl script running on vMA appliance) for long time and it never had problems before the upgrade. There is nothing in the syslog at the time, but I can observe tons (150+) smbd processes in "D" state (from "man ps": Uninterruptible sleep (usually IO)). The problem is unlikely related to samba since there is 0 windows related traffic at the time - only NFS. It looks like the system locks during intensive NFS I/O. Though there was one or two nights when the backups completed with no problems. Does any of you use unraid 5.0b6a as NFS server intensively? Have you ever seen what I described? Is there any known problems with NFS in the current version?

Thanks! It was unraidweb package. Do you have any 3rd party utlities/php servers installed? Essentially the PHP server you're running isn't recognising php short tags.

Has anybody seen this after upgrade from 4.7? I've followed the instructions in Release Notes. Basically, the GUI is broken after the upgrade as shown in the attachment.

They are counting on it being a hassle, and on you letting it go because of that. Just read the fine print and you will understand why it is not worth it... http://www.apc.com/support/service/equipment_protection_policy.cfm Apparently you have to register your UPS within 10 days after purchase. How many people do that?