PDA

View Full Version : SLES SP 2 Update Boot Hangs on loading yast2



elphantasmo
10-Dec-2012, 16:58
After updating from SLES 11 SP1 (x64) to SP2 via DVD, the boot stops on loading yast2. Pressing "ctrl-C" makes it continue with no ill effects, seemingly. We're using it to run ZENworks 11.2.2, with a local Sybase database. This area is certainly not a strength of mine. Where do I need to look to see why this is happening? If someone wants to see some log files, simply let me know.

malcolmlewis
10-Dec-2012, 17:23
On Mon 10 Dec 2012 04:04:02 PM CST, elphantasmo wrote:


After updating from SLES 11 SP1 (x64) to SP2 via DVD, the boot stops on
loading yast2. Pressing "ctrl-C" makes it continue with no ill effects,
seemingly. We're using it to run ZENworks 11.2.2, with a local Sybase
database. This area is certainly not a strength of mine. Where do I
need to look to see why this is happening? If someone wants to see some
log files, simply let me know.




Hi
Stopping on YaST on the console during boot?, that sounds like the auto
configuration didn't complete after the update.....

There are logs down in /var/log/YaST2 which may indicate the error.

--
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop
up 4 days 2:16, 4 users, load average: 0.17, 0.18, 0.11
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

elphantasmo
12-Dec-2012, 17:25
Here's a bit from the \var\logs\y2log

2012-12-07 11:22:19 <0> linux(26785) [scr] ScriptingAgent.cc(parseConfigFiles):91 Can't open directory /y2update/scrconf for reading: No such file or directory
2012-12-07 11:22:19 <0> linux(26785) [scr] ScriptingAgent.cc(Sweep):436 Scripting agent searching SCRs in /root/.yast2/scrconf
2012-12-07 11:22:19 <0> linux(26785) [scr] ScriptingAgent.cc(parseConfigFiles):86 Y2SCRComponent::parseConfigFiles (/root/.yast2/scrconf)
2012-12-07 11:22:19 <0> linux(26785) [scr] ScriptingAgent.cc(parseConfigFiles):91 Can't open directory /root/.yast2/scrconf for reading: No such file or directory
2012-12-07 11:22:19 <0> linux(26785) [scr] ScriptingAgent.cc(Sweep):436 Scripting agent searching SCRs in /usr/share/YaST2/scrconf
2012-12-07 11:22:19 <0> linux(26785) [scr] ScriptingAgent.cc(parseConfigFiles):86 Y2SCRComponent::parseConfigFiles (/usr/share/YaST2/scrconf)

and

YaST2/ProductFeatures.
2012-12-07 11:22:21 <3> linux(26785) [agent-ini] IniParser.cc(getTimeStamp):923 Unable to stat '/etc/YaST2/ProductFeatures': No such file or directory
2012-12-07 11:22:21 <3> linux(26785) [agent-ini] IniParser.cc(getTimeStamp):923 Unable to stat '/etc/YaST2/ProductFeatures': No such file or directory
2012-12-07 11:22:21 <2> linux(26785) [agent-ini] IniParser.cc(UpdateIfModif):906 Data file '/etc/YaST2/ProductFeatures' was changed externaly!
2012-12-07 11:22:21 <3> linux(26785) [agent-ini] IniParser.cc(parse):554 Can not open /etc/YaST2/ProductFeatures.


I'm not sure if these items are helpful, and these were the only references to yast2 in a couple of log files that seemed suspect to me. This problem isn't critical but it sure is annoying.

malcolmlewis
12-Dec-2012, 18:19
On Wed 12 Dec 2012 04:34:01 PM CST, elphantasmo wrote:


Here's a bit from the \var\logs\y2log

2012-12-07 11:22:19 <0> linux(26785) [scr]
ScriptingAgent.cc(parseConfigFiles):91 Can't open directory
/y2update/scrconf for reading: No such file or directory
2012-12-07 11:22:19 <0> linux(26785) [scr] ScriptingAgent.cc(Sweep):436
Scripting agent searching SCRs in /root/.yast2/scrconf
2012-12-07 11:22:19 <0> linux(26785) [scr]
ScriptingAgent.cc(parseConfigFiles):86 Y2SCRComponent::parseConfigFiles
(/root/.yast2/scrconf)
2012-12-07 11:22:19 <0> linux(26785) [scr]
ScriptingAgent.cc(parseConfigFiles):91 Can't open directory
/root/.yast2/scrconf for reading: No such file or directory
2012-12-07 11:22:19 <0> linux(26785) [scr] ScriptingAgent.cc(Sweep):436
Scripting agent searching SCRs in /usr/share/YaST2/scrconf
2012-12-07 11:22:19 <0> linux(26785) [scr]
ScriptingAgent.cc(parseConfigFiles):86 Y2SCRComponent::parseConfigFiles
(/usr/share/YaST2/scrconf)

and

YaST2/ProductFeatures.
2012-12-07 11:22:21 <3> linux(26785) [agent-ini]
IniParser.cc(getTimeStamp):923 Unable to stat
'/etc/YaST2/ProductFeatures': No such file or directory
2012-12-07 11:22:21 <3> linux(26785) [agent-ini]
IniParser.cc(getTimeStamp):923 Unable to stat
'/etc/YaST2/ProductFeatures': No such file or directory
2012-12-07 11:22:21 <2> linux(26785) [agent-ini]
IniParser.cc(UpdateIfModif):906 Data file '/etc/YaST2/ProductFeatures'
was changed externaly!
2012-12-07 11:22:21 <3> linux(26785) [agent-ini]
IniParser.cc(parse):554 Can not open /etc/YaST2/ProductFeatures.


I'm not sure if these items are helpful, and these were the only
references to yast2 in a couple of log files that seemed suspect to me.
This problem isn't critical but it sure is annoying.




Hi
If you use zypper from the command line, I wonder if it's missed some
YaST updates...


zypper ref
zypper lu



--
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop
up 15:56, 3 users, load average: 0.00, 0.03, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

elphantasmo
12-Dec-2012, 20:44
Hi
If you use zypper from the command line, I wonder if it's missed some
YaST updates...


zypper ref
zypper lu



--
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop
up 15:56, 3 users, load average: 0.00, 0.03, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU



Didn't look like any of the updates were yast related, just some new ones. I'll restart the server a little later, just in case.