cron after Update - "stdin: is not a tty"

Same with me.... , it happens after last install openmediavault-backup (3.9) - seems to me. Fix is for OMV3 this?: mesg: ttyname failed: Inappropriate ioctl for device Thank you.

Running openmediavault-cron-apt in command line finnishes well /no output, no error/.

/root/.profile

if [ "$BASH" ]; then
  if [ -f ~/.bashrc ]; then
    . ~/.bashrc
  fi
fi


mesg n

Votdev recomend to add the "|| True" at the end:

mesg: ttyname failed: Inappropriate ioctl for device

Quote from Denqbar

test -t 0 && mesg n true

I also got that email after the update to the latest omv 3.0.95:

[omv] Anacron job 'cron.daily' on omv


/etc/cron.daily/openmediavault-cron-apt:
stdin: is not a tty

and changed the content of "/root/.profile" from:

# ~/.profile: executed by Bourne-compatible login shells.


if [ "$BASH" ]; then
  if [ -f ~/.bashrc ]; then
    . ~/.bashrc
  fi
fi


mesg n

to:

# ~/.profile: executed by Bourne-compatible login shells.


if [ "$BASH" ]; then
  if [ -f ~/.bashrc ]; then
    . ~/.bashrc
  fi
fi


test -t 0 && mesg n || true

I hope that is what should be done.

Greetings Hoppel

Hello,

I have the same problem since last sunday 24 december.

Quote

/etc/cron.daily/openmediavault-cron-apt:

stdin: is not a tty

When I try to run on a console /etc/cron.daily/openmediavault-cron-apt, it seems to wait for some keyboard input and I must use Cttr+C to stop the process.

I try to add | | true but it doesn't change anything

Is anyone have an idea ?

Best regards

I described the solution above. This works as expected for me.

thak you for your answers.

I try to update the /root/.profile as explain above but nothing changes and it works. Very sorry for the mistake.
When I run manually from the console /etc/cron.daily/openmediavault-cron-apt, it works fine. After a few moments, the prompt comes back.

Thank you very much for your help

Quote from MerAnges

thak you for your answers.

I try to update the /root/.profile as explain above, but nothing changes.
When I run manually from the console /etc/cron.daily/openmediavault-cron-apt, it works fine. After a few moments, the prompt comes back.

Thank you very much for your help

do you try to reboot your NAS , so changes in /root/.profile become active?.

Quote from raulfg3

do you try to reboot your NAS , so changes in /root/.profile become active?.

I didn’t reboot my omv machine, it works anyway.

Oh I'm very sorry , I don't change all my previous message when I post it the first time.

WIth the modification It works !

I’m encountering the same error on a freshly installed omv 3. If this is something caused by an update, shouldn’t it be fixed in omv source instead of by the user?

Can we not fix this for everyone with a patch update?

Could someone explain what this error means and is it critical to fix? I understand there is a fix listed above, but as a complete noob to linux I have no idea how to actually make the changes and save them.

Thank you for the clear and concise answer, I will give that a try.