I have installed OMV for the first time and are only configuring so far. The autoshutdown plug in crashes repeatedly.
From the log file, it looks like a problem with the priority variable. I don't know what to do about it.
Autoshutdown crashes
-
- OMV 5.x
- gelöst
- Phasetone
-
Phasetone
Hat das Label OMV 5.x hinzugefügt. -
Hi, yet this is a bit odd, can I have a copy of your /etc/autoshutdown.conf. Also can you modify the script that is running /usr/sbin/autoshutdown and change line 1 to "#!/bin/bash -x" (you will need to be root to do this) this will show what the script is doing just prior the problem.
-
hmm, this work for me just find however, I really don't like the current _log function. cany you try replacing the current _log function with the following (again you have to edit the /usr/sbin/autoshitdown script by hand:
Code
Alles anzeigen_log() { local -r user="$(id -nu "$(< "/proc/self/loginuid")" 2>/dev/null || true)" local -r tag="$(basename "${0}")" local -r priority="${1%%: *}" local message="${FUNCNAME[1]}(): ${1#*: }" [ "${FAKE:-}" == "true" ] && message="FAKE-Mode: ${message}" local -r message="${user:-${USER}}: ${priority}: '${message}'" [ "${LOG_STDOUT:-}" != "false" ] && echo "$(date "+%b %e %H:%M:%S") $(hostname -s ) ${tag}[${$}]: ${message}" [[ "${SYSLOG:-}" == "true" || "${2:-}" == "force" ]] && logger --id="${$}" -t "${tag}" -p "syslog.${priority,,}" "${message}" return 0 }Hopefully this will work for you without issues but let see. let me know how you get on.
-
hi, this is not all that useful as it the salt output not the service output, but I am not entirely surprised this is not working as I am missing something on your system. The script should have worked as the original failure would kill the script on all systems and we not seeing this. However, this does not mean there is no issue.
So I going to need a few more bit of info form you, it also possible the script edit you did has an issue.:
1. Can I have the output form the failed service. this can be obtained from 'sudo journalctl -u autoshutdown.service' this should contain were the script is now failing.
2. Can I have the output of: 'cat /etc/default/locale' I will mimic your localisation just to see if that the issue.
3. Less useful but I just what to check: 'bash --version'
1. Is the most important as i need to know why the script is now falling.
-
ok so form this is looks as if the script in not working at all. can you run it directly?
'sudo /usr/sbin/autoshutdown'
-
I still cannot re-create your issue even with localisation changes. However this has lead me to finding postfix issue with some of the regex expressions that can cause issues. So can you test the below?
Here how to do it, this will require you to do this all in a shell.
Code$ wget https://raw.githubusercontent.com/nrandon/openmediavault-autoshutdown/test/usr/sbin/autoshutdown $ chmod +x autoshutdown $ sudo cp autoshutdown /usr/sbin/autoshutdownTo test first run the scripts directly directly:
Code$ sudo /usr/sbin/autoshutdownHopefully this will work. If is does not run add the "#!/bin/bash -x" and send the output close to were it stopped as you have done before and I try to see if i can see what up. If it work then use the OMV GUI and start the service as you have before and i submit a patch with a set of fixes.
-
Access denied........ ? to what the wget ?
-
ok so that an improvement. to know what going on in the post stuff i need a little more info. (this is why the script has a debug/verbose mode) turn on debug in the script and it should give the raw port info it found to determine there was activity. if you post the section with debug on i can tell you what it thinks is going on or if you found another bug
-
no Verbose=Debug this is historic
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
