mesg: ttyname failed: Inappropriate ioctl for device
-
- OMV 4.x
- gelöst
- macom
-
-
-
The shebang is in my file. I got this message yesterday for first time (4.0.15-1). Ran manually as root, didn't output the error. I'll report back tomorrow when the next daily run is scheduled
-
-
The shebang is in the file.
Latest version 4.0.15-1.If I run the script as root I do not get an error message in the terminal. Need to see if I get the mail.
-
Can not reproduce this problem when i setup a scheduled cron job. Simply create a job that is executed every 5 minutes with the command 'cron-apt'.
Nevertheless i have removed the login shell from the script because it is not needed anymore in OMV4 (PROXY settings are configured via APT now, so there is no need to source profile.d via login shell).
-
I get a message with the error then the message with the packages available.
Again if I run manually no error in terminal and I get only the message with packages this time no ioctl error.
-
-
Yesterday I applied the fix from Volker. No mail today.
-
-
-
-
You can apply it there, too. But use the whole command line including the true.
-
Some days ago I upgraded my system from omv3 to omv4. At the moment everything I need works as expected, but I also got this Email:
Code[omv4.localdomain] Anacron job 'cron.daily' on omv4 /etc/cron.daily/openmediavault-cron-apt: mesg: ttyname failed: Unpassender IOCTL (I/O-Control) für das Gerät
I did exactly what I did under omv3 to solve the behavior and what I described here:
cron after Update - "stdin: is not a tty"
Thanks guys!
-
If also got this message with the latest OMV4. Could the provided fix not included with the next release?
-
-
If also got this message with the latest OMV4. Could the provided fix not included with the next release?
No
-
Not so much information please.
Why "No"?
-
As far as I understand the issue is caused by Debian and not by OMV. So it can only be fixed by Debian.
-
-
Thanks. This answer is more helpful.
-
I'm having this message too, hope it will resolve it!
-
The above described solution solves the issue.
Greetings Hoppel
-
-
In the syslog section i have this line every 1 minute:
CRON[variable number]: (root) CMD (test -x /usr/sbin/wakealarm && /usr/sbin/wakealarm > /dev/null 2>&1)this is my /root/.profile :
Code
Alles anzeigen# ~/.profile: executed by Bourne-compatible login shells. if [ "$BASH" ]; then if [ -f ~/.bashrc ]; then . ~/.bashrc fi fi test -t 0 && mesg n || true
is it normal? -
up, why i'm getting the log flooded by that line?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!