jowi

Found it; maybe others can be helped with this as well. Had to add the line add_header X-Frame-Options "SAMEORIGIN"; to the "default" config file in /appdata/nextcloud/nginx/site-confs folder. So had nothing to do with nginx proxy manager as it seems

I'm having issues with nextcloud complaining about the x-frame-options not being set to SAMEORIGIN. I've added the following line to the advanced settings for my proxy host config in nginx: add_header X-Frame-Options "SAMEORIGIN" always; But doesn't work. Found this topic, seen some mentions about the same issue but couldn't find any solution other than the above line? What am i missing?

Looked for ipmi logging, but can’t find them? Do i need to run some cmdline ipmi thingy on the server to collect or start ipmi logging? I’m using supermicro’s ipmiview windows app as ipmi client. *edit found ipmi log settings in bios, will take a look, is probably disabled. *edit yes it was. Enabled it.

yeah i know but the server crashing while roon was rebuilding the library after losing connection to the rooncore (which happens a lot...), occured at least two times, maybe even 3 times. Not much weird stuff running on the server, sabnzbd, nextcloud, unify controller, pihole, sonarr, thats about it. 32Gb mem, quadcore xeon 1230. no vm’s running. syslog shows NOTHING. Is there a way to get roon logging somewhere persistent?

This docker has a very serious issue, it takes down my array sometimes... it starts with the remote app losing the roon core, you have to reselect it, login again, and re-add your folders. Then it starts indexing, and crashes... and takes my complete unraid server with it. Seriously. No shares, no gui, no dockers, no plugins, nothing, it is dead. It kills my server. Have to hard reset (yikes) or use IPMI to reset. Any idea on what it can be? Some logging i can look into?

Yes, if i had the expertise. I can do c# .net core etc programming and some minor python, but somehow i think that is not needed here. Also linux is not my thing. If you’re suggesting i am not allowed to comment unless i contribute? F*** you. That is not up to you.

User scripts has grown from a quickly bolted together handy but buggy tool into a substantial part of unraid that a lot of users have use for, and it needs and deserves a lot of rework and refactoring and attention to take it to a higher level.

Yeah ok but why then use the user script module anyway at all, and not just run my python script (like i did before....) as a cron job or daemon....

Ok, but such a process would be started by.... the user script plugin and... the user script plugin sometimes kills your process for no apparent reason (as far as i can. tell) also this monitoring process, with... a sigkill bullet so, how do we monitor the monitoring process... I had this python script built as a daemon years ago, and it was started by adding it to the go file. But since the latest unraid version, the python daemon library i used, doesn’t work anymore, and i couldnt be bothered finding out why, so i just converted it to a user script. I think the request for sending sigterm first and sigkill a few seconds later, solves everything.

Exactly... THAT is the point. Unraid user script ALWAYS kills user processes with SIGKILL... also when you manually stop the script. And sometimes the script gets killed off for no reason by unraid. And there is no way to react to that. You just get a bullet in the head.

This script runs 24/7... i don't want to create GB's of logging... so i only log errors. Which is best practice anyway.

But the python script doesn't write to stdin or stdout...? It just sends commands over IP to my TV, and if an exception is thrown, it sends an email with the exception...

The python script catches any exceptions and sends an email with the exception message.... that also doesn't happen, so i don't why returning an error would work? It just looks like the process gets shot in the head. Immediate death.

So, why can i set all kinds of resolutions in my (spaceinvader inspired) Windows 10 VM, but i can only select 1920x1080 in OSX? (even if i set the clover? bios to 2560x1600) What is the trick for adding more resolutions in OSX? I’m using vm’s through chrome remote desktop btw so remote always.

My background user script just got stopped (by unraid i assume) for no apparent reason, did not do it myself, also wasnt an exception in the python code, because that would send me an email and gets logged. Also, in that case only the python script would get killed not the .sh etc. In this case, the whole user script ‘chain’ was gone from process list. Not sure if there is some syslogging that i could attach for more clarity?

I understand there is no way to respond to a sigkill...

Looks like aborting a script does not kill everything. I'm using a user script that 'bashes' a shell script, and that shell script in turn runs a python script: #!/bin/bash #backgroundOnly=true #arrayStarted=true bash /boot/custom/kuroautomode.sh (I don't know how to use bash to call python directly? So this is how i do it. bash is needed, the .sh and .py reside on the usb stick in a subfolder under boot folder) When this is started, proceslist will show 4 processes: root 22117 0.0 0.0 104624 26196 ? SL Aug03 0:00 /usr/bin/php /usr/local/emhttp/plugins/user.scripts/startBackground.php /tmp/user.scripts/tmpScripts/kuroAutoMode/script root 22118 0.0 0.0 3840 2916 ? S Aug03 0:00 sh -c /tmp/user.scripts/tmpScripts/kuroAutoMode/script >> /tmp/user.scripts/tmpScripts/kuroAutoMode/log.txt 2>&1 root 22119 0.0 0.0 3840 2808 ? S Aug03 0:00 /bin/bash /tmp/user.scripts/tmpScripts/kuroAutoMode/script root 22120 0.0 0.0 3840 2916 ? S Aug03 0:00 bash /boot/custom/kuroautomode.sh root 22121 0.0 0.0 18716 14564 ? S Aug03 0:02 /usr/bin/python /boot/custom/kuroautomodecmdline.py Now, when i abort the user script from within unraid, proclist still shows: root 22119 0.0 0.0 3840 2808 ? S Aug03 0:00 /bin/bash /tmp/user.scripts/tmpScripts/kuroAutoMode/script root 22120 0.0 0.0 3840 2916 ? S Aug03 0:00 bash /boot/custom/kuroautomode.sh root 22121 0.0 0.0 18716 14564 ? S Aug03 0:02 /usr/bin/python /boot/custom/kuroautomodecmdline.py So it only aborts the script logging, nothing else. Everything else keeps running. If i restart the user.script, i get everything running 2x, 3x, 4x etc. if i don't manually remove it. Am i doing something wrong or is this an issue?

Is this also true for the seek error rate? I got pretty scared adding my new 16TB seagate to my array, preclearing got the read error rate up and up... luckily i got to this post running the smartctl command shows 0 read errors, but the seek error rate still has high, changing numbers?

Another new & exiting issue. If i start vnc i get the message 'Guest has not initialised the display (yet)"... you know what? I quit. It's just not worth the trouble and frustration.

Again, see my comment above. The resolution there does not seem to matter. Only running vnc fullscreen BEFORE you boot osx, prevents messy video. If i set video in uefi bios to 2560x1600 (native res of monitor) osx still starts up in 1920x1080, and ONLY if i run vnc fullscreen. There also is no option to choose any other resolution in osx other then 1920x1080 regardless what resolution i select in uefi.

I think you mean that once inside the clovis “menu” you need to select restart clovis, THEN hit F2 to get in the actual bios. That is the only way i can get in some bios and get to set a resolution. But... what resolution i set, if i do NOT run clovis/vnc in full screen mode, the video is messed up. So apparently you must go full screen BEFORE you boot osx. Whatever resolution i choose, if i run vnc in a window, video will be messed up. Second, if i select 2560x1600 (the res of my actual monitor) osx starts in 1920x1080 and i can not select any other resolution in osx. There is 1 option and that is 1920x1080... how do i get to use other resolutions?

What is 'it'? When you start the vm's (clover) bios? F2 doesnt do anything. If you hit enter so OSX boots, F2 also does NOT do anything. Please explain clearly what we need to do?

Doesn’t work for me as well. High Sierra, the share doesn’t show up in timemachine disk select settings. Also tried the fruit option, didn’t work. Editing the avahi services smf file made the share show up in timemachine, but after selecting it, the message showed up that the drive was not capable... this whole timemachine stuff on apple is broken on so many levels, it's not even funny anymore.

Installing the temp plugin on 6.8.3 shows: Unraid version too high, requires at most version 6.7.2... Is this plugin obsolete?

I'm running some python scripts on array startup; each script sends an email when it is started, and also when an exception occurs, but also when the program exits, using the atexit exit handler (https://medium.com/better-programming/create-exit-handlers-for-your-python-appl-bc279e796b6b) If i run the python script manually, ctrl-c will indeed make the program send an email that it has been stopped, but if i call the python script from a user-script, and stop the program from user-script, no exit email is being sent, the exit handler doesn't seem to be called. I guess this has to do with the way user-script runs these in the background, is there another way to hook up to some exit function in python so this works?