11.4 RC1

user · February 25, 2011, 12:40am

Installed (updated thru YaST))to RC1 this last week. Get message on
shutdown that /etc/init.d/halt.local is missing. Tied find what provides
it but I must be doing something wrong because I cannot find it.

Can anyone point me in the right direction?

Thanks

jdmcdaniel3 · February 25, 2011, 2:34am

This is a script file you could create. It seems to do nothing by default.

#! /bin/sh
#
# Copyright (c) 2002 SuSE Linux AG Nuernberg, Germany.  All rights reserved.
#
# Author: Werner Fink, 1998
#         Burchard Steinbild, 1998
#
# /etc/init.d/halt.local
#
# script with local commands to be executed from init on system shutdown
#
# Here you should add things, that should happen directly before shuting
# down.
#

Copy and past this code into a text editor such as kwrite, if you use KDE with the menu Run Command:

kdesu kwrite /etc/init.d/halt.local

Save the file and then open a terminal session and enter the command:

sudo chmod +x /etc/init.d/halt.local

To make the file executable and then you got it. I am not sure why this file would be missing in action.

Thank You,

user · February 25, 2011, 3:40pm

jdmcdaniel3 wrote:

>
> This is a script file you could create. It seems to do nothing by
> default.
>
>
> Code:
> --------------------
> #! /bin/sh
> #
> # Copyright (c) 2002 SuSE Linux AG Nuernberg, Germany. All rights
> # reserved.
> #
> # Author: Werner Fink, 1998
> # Burchard Steinbild, 1998
> #
> # /etc/init.d/halt.local
> #
> # script with local commands to be executed from init on system
> # shutdown
> #
> # Here you should add things, that should happen directly before
> # shuting down.
> #
>
> --------------------
> Copy and past this code into a text editor such as kwrite, if you use
> KDE with the menu Run Command:
>
>
> Code:
> --------------------
> kdesu kwrite /etc/init.d/halt.local
> --------------------
> Save the file and then open a terminal session and enter the command:
>
>
> Code:
> --------------------
> sudo chmod +x /etc/init.d/halt.local
> --------------------
> To make the file executable and then you got it. I am not sure why
> this file would be missing in action.
>
> Thank You,
>
Thanks I will create the file. I was curious if this missing script was
the reason my system never shuts down, gets a powerdown message and
hangs.

I also thought of coping the one from 11.3 but wasn’t sure if they were
the same. I’ll just cheate the script.

Thanks

robin_listas · February 25, 2011, 8:50pm

On 2011-02-25 15:40, upscope wrote:

> I also thought of coping the one from 11.3 but wasn’t sure if they were
> the same. I’ll just cheate the script.

The content of the file is irrelevant, a single line like this will do - or
no file at all:

Code:

#!/bin/sh

If the file exists, it will run. In fact, if you see an error that the file
does not exist, it is a bug that you should report. An informative message
is OK.

This file is your file, that’s what the “local” in it’s name means. You
create it if you need it. YaST creates it somehow just for your convenience
(it is not in any rpm).

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

user · February 26, 2011, 6:14pm

Carlos E. R. wrote:

> On 2011-02-25 15:40, upscope wrote:
>
>
>> I also thought of coping the one from 11.3 but wasn’t sure if they
>> were the same. I’ll just cheate the script.
>
> The content of the file is irrelevant, a single line like this will do
> - or no file at all:
>
> Code:
> --------------------
> #!/bin/sh
> --------------------
>
> If the file exists, it will run. In fact, if you see an error that the
> file does not exist, it is a bug that you should report. An
> informative message is OK.
>
>
> This file is your file, that’s what the “local” in it’s name means.
> You create it if you need it. YaST creates it somehow just for your
> convenience (it is not in any rpm).
Thanks. I new what local meant. I was trying to see if it being lost,
was preventing my system from shutting down. I look again today after
putting the script in and if it still gives the message I will report
the bug. system

jdmcdaniel3 · February 26, 2011, 6:43pm

openSUSE 11.4 RC2 is now out and only 12 days till the final release. Perhaps you should try to load or upgrade to the newer version instead?

Thank You,

user · February 27, 2011, 6:33pm

jdmcdaniel3 wrote:

>
> openSUSE 11.4 RC2 is now out and only 12 days till the final release.
> Perhaps you should try to load or upgrade to the newer version
> instead?
>
> Thank You,
>
I keep my 11.4 up todate. Plan is to do complete clean install after
release of final version.

Thanks for your help.

bisers_toilov · March 15, 2011, 10:57pm

I have the same problem on openSUSE 11.4 Final. Any solution?

Thanks in advance.

DenverD · March 15, 2011, 11:38pm

On 03/15/2011 11:06 PM, bisers toilov wrote:
>
> I have the same problem on openSUSE 11.4 Final. Any solution?

check the bug…surely SOMEONE logged a bug…maybe…that is the whole
purpose of running Milestones and RCs…

–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.1.8, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

eng-int · March 16, 2011, 1:10pm

# touch /etc/init.d/halt.local

I have run a number of upgrades and installs and this file has always been installed. Perhaps you are doing something out of th ordinary?

purevw · March 28, 2011, 3:55am

Is the file actually missing? During shutdown, mine shows a very similar message, but it appears that “missing” appears one line below Halt.Local in the sequence. The file is on my system. I am just curious if this is the same problem. I am having file system damage during each shutdown because apparently the drives are not being correctly dis-mounted during shutdown. Trying halt -h makes no difference as they are SATA drives. This problem did not exist until a “zypper dup” upgrade from 11.3 to 11.4 today. Every time I boot, fscheck goes through about 300 lines because the file system is not clean.

user · March 28, 2011, 10:59pm

purevw wrote:

>
> Is the file actually missing? During shutdown, mine shows a
very similar
> message, but it appears that “missing” appears one line
below Halt.Local
> in the sequence. The file is on my system. I am just
curious if this is
> the same problem. I am having file system damage during
each shutdown
> because apparently the drives are not being correctly dis-
mounted during
> shutdown. Trying halt -h makes no difference as they are
SATA drives.
> This problem did not exist until a “zypper dup” upgrade
from 11.3 to
> 11.4 today. Every time I boot, fscheck goes through about
300 lines
> because the file system is not clean.
>
I get that same message. I stopped the screen and it looks
like the message is halt.local is missing but on 11.4 the
file is there. I was also gettint it on 11.3 and the file was
gone. I did a clean install of everything on 11.4 after I
wiped out my 11.3 install because I hit a wrong key.

I’ve been seeing this message since an upgrade to 11.3. When
I first installed 11.4 GM it worked a couple of times and
then stopped shutting down my system. restart works fine.

If you find a solution please post it. I’ve also changed from
auto to poweroff in etc/sysconfig/system/halt and it still
will not powerdown. 11.2 was working with no problems before
I deleted it.

–
Russ
openSUSE 11.4 MS1 (2.6.37.1-1.2-desktop)|Platform Version
4.6.1 (4.6.1) “release 390”|Intel core2duo 2.5 MHZ,|8GB DDR3|
GeForce 8400GS (NVIDIA-Linux-x86_64-270.18)

elksi · April 14, 2011, 3:27pm

I have also exactly the same issue. My separate /home partition as well as an always mounted external disk (through entry on fstab) are reported unclean on every boot.

I have also upgraded from 11.3.

Is a bug has been reported?

lwfinger · April 14, 2011, 5:11pm

On 04/14/2011 08:36 AM, elksi wrote:
>
> I have also exactly the same issue. My separate /home partition as well
> as an always mounted external disk (through entry on fstab) are reported
> unclean on every boot.
>
> I have also upgraded from 11.3.
>
> Is a bug has been reported?

You need to check that.

When the system is shutting down, press the <ESC> key to get rid of the
“bootsplash” screen. Is there any mention of any of the disk partitions being
“busy” when unmounting?

This is not a general problem. Something particular on your system is not
shutting down properly.

elksi · April 14, 2011, 6:17pm

I have checked the messages on shutdown. There is no “busy” on any partition. Also others users are affected as well:

After upgrade to 11.4 hard drives not properly unmounted during halt

lshantz · September 20, 2011, 2:33am

Just thought I’d add to this thread. I did a fresh install months ago. Just now getting around to stamping out boot and shutdown errors. I did create a file in /etc/init.d/halt.local. I actually just did a “touch”. Rebooted and got the same message. However… I notice that it says
halt.local done
done
missing
done

So something else is happening. It seems to be forking out and doing something else at this point.

One thing I thought was interesting is that I had a blank halt.local. After reboot it had text entered into it.

Here is the text:

 #! /bin/sh

> #
> # Copyright (c) 2002 SuSE Linux AG Nuernberg, Germany. All rights
> # reserved.
> #
> # Author: Werner Fink, 1998
> # Burchard Steinbild, 1998
> #
> # /etc/init.d/halt.local
> #
> # script with local commands to be executed from init on system
> # shutdown
> #
> # Here you should add things, that should happen directly before
> # shuting down.

It is clearly not serious, but perplexing.

markus9957 · January 16, 2012, 8:57am

I had the same problem since 11.3/32, that I didn’t like the red “missing” while shutting down the system.
Difference: the shutdown worked anyway.

I found the answer in the german linux-club: LINUX • Thema anzeigen - [gelöst] nach zypper dup auf 11.4 running halt.local missing

Original text:
/etc/init.d/boot.device-mapper bzw. über den entsprechenden Link in /etc/init.d/boot.d/
Und das missing ist keine Fehlermeldung sondern ein Hinweis, das es keine Methode gibt den entsprechenden Dienst/Funktion anzuhalten.

Wenn die rote Meldung stört /etc/init.d/boot.device-mapper in einen Editor öffnen und folgende Stelle suchen:

Code: Alles auswählen
stop)
rc_failed 3
rc_status -v
;;

und den Wert hinter rc_failed nach belieben (0-7) ändern. Zum Testen einfach das Sript mit dem Parameter stop aufrufen, es macht dann nichts anderes als die Meldung ausgeben:

/etc/init.d/boot.device-mapper stop

Tooltime
Advanced Hacker
Advanced Hacker

Beiträge: 1292
Registriert: 28. Mai 2008, 16:49

Translated text: go to the file
/etc/init.d/boot.device-mapper resp. the related Link in /etc/init.d/boot.d/
The “missing” is no error message but a hint, that there is no service/function to stop this task.

If you don’t like the red message, open /etc/init.d/boot.device-mapper with an Editor and go to these lines:

stop)
     rc_failed 3
     rc_status -v
     ;;

and change value behind rc_failed in a different value (0-7). For a test just call the Sript with the Parameter stop. The following message will appear:

/etc/init.d/boot.device-mapper stop

Have fun!

OpenSusE 11.4 32 bit
KDE SC 4.7
AS-Rock ion 330 HD