Hi All,

We have an issue mentioned above in Subject.
Long story short, we have a replica job using Veeam, when I turned on the cloned / replicated VM I got the error message shutdown invalid, I shutdown with shutdown -g0 - y again in hope we could get rid of the error message, but it is still there.
How can I get rid of the error message?
Thanks a lot in advance.

Best Regards

On systemd distros, shutdown is just a symlink to /bin/systemctl. Try shutting down using systemctl poweroff if using a systemd distro.

Hi mrmazda,
Thanks for the response. Unfortunately they don't use systemctl so I can't use poweroff

Best Regards

What does man shutdown have to say? Neither -g nor -y are available options here in openSUSE.

Hi Mrmazda

man shutdown:
Shutdown [-y] [-ggrace_period] [-iinit_state]
Other recommended system state definitions are:
State 0
State 1
State s, S
State 5
State 6

So you know it is UnixWare 7 Release 7.1.4

Best Regards

What happens with shutdown -g0 -y -i0 or shutdown -g0 -y -i6, or simply leaving out the gap between - and y?

I suggest that you try:

shutdown -y now

Hi jailbait and mrmazda,

Unfortunately, none of them helped.
Best Regards

I'm out of ideas. The closest thing I ever used to any Unix flavor was Xenix, 35 years ago.

I thought that looked familiar. I haven't seen that form of shutdown since running Consensys (SysV4.2) on my old 486.

What is the default for the '-i' switch? The command you're using is telling shutdown to use 0 minutes for the grace period but I'm not sure if you've told it that you want to go to level 0. The error message you're seeing may simply be a Unixware's cryptic way of saying "target run level unknown".

Just for the heck of it, issue
(hoping Unixware implemented the 'which' command.)

I'm wondering if you're inadvertently running someone's old shutdown wrapper script (with an unfortunate name) and the arguments aren't the same as the system's shutdown command. Stranger things have been done.

Anyway, I would expect to use something like:
to shut the system down NOW with no confirmation.

HTH...

There used to be a real binary shutodwn, but then a script called shutdown that actually does a more graceful shutdown. You have to identify (like rnturn said) and identify the shutdown in the script. Often, it is a assumed PATH that doesn't include or has the wrong ordering. If you figure it out, just make it full path, like /usr/sbin/shutdown instead of assuming a PATH search.