[Bug 227742] New: fatal error while booting 1st time opensuse GM i386
https://bugzilla.novell.com/show_bug.cgi?id=227742 Summary: fatal error while booting 1st time opensuse GM i386 Product: openSUSE 10.2 Version: Final Platform: 32bit OS/Version: SuSE Linux 10.1 Status: NEW Severity: Blocker Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: h.weebers@kpnplanet.nl QAContact: jsrain@novell.com After downloading DVD, the install program replaced files. Then at restart fot the first time, a fatal error is reported. /etc/initscript: line 55: +: syntax error: operand expected (error token is " +") On a second disk I can still boot SUSE linux 10.1. What can be done to repair initscript? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |werner@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 werner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|werner@novell.com |garloff@novell.com ------- Comment #1 from werner@novell.com 2006-12-12 03:07 MST ------- This script or better file is part of package ulimit, reassign to maintainer. Remark: the syntax TOT=$(($MEMTOT+$SWPTOT)) is allowed even in a POSIX bourne shell as long as both variables MEMTOT and SWPTOT are set by the previous sed commands used for parsing /proc/meminfo. Nevertheless, IMHO the two sed command calls should be replaced by one `while read; case ... esac; done < /proc/meminfo' to avoid two fork/execev. Beside this the values of MEMTOT and SWPTOT should not be zero. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 ------- Comment #2 from h.weebers@kpnplanet.nl 2006-12-17 05:47 MST ------- Created an attachment (id=110033) --> (https://bugzilla.novell.com/attachment.cgi?id=110033&action=view) Solution in initscript for removing blocking error. Comments are places in the text around processing '/proc/meminfo'. At first start up at installation, /proc/meminfo is empty. So all proceessings should be swapped. My opensuse 10.2 is running now. But What about other downloads? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 ------- Comment #3 from garloff@novell.com 2006-12-18 04:33 MST ------- I agree that the parsing of /proc/meminfo can be improved avoiding sed. I'd go for a solution avoiding to fork sed or awk ... It can also be made more error tolerant. However, I'm really puzzled by the problem referred to in the report. If /proc/meminfo exists, the kernel also publishes reasonable data there. An empty /proc/meminfo is not possible as far as I can tell, unless you have not mounted procfs. And even then you'd need to be malicious to your system by doing something like touch /proc/meminfo. Who would do that? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 h.weebers@kpnplanet.nl changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |h.weebers@kpnplanet.nl ------- Comment #4 from h.weebers@kpnplanet.nl 2006-12-18 13:44 MST ------- Dear Kurt, Its not my hobby to write computerprogramms. But pass a puzzle to me! For your info, I downloaded opensuse 10.2-GM-i386 and stated upgrade. After swappung files, Suse 10.2 asks for rebooting. And so it happened. But then the problem occured. I searched internet for programming codes. I changesd to boot suse 10.1 for analyzing the problem. I couldn't understand the lines with 'sed', so I searched an other way to extract values of MemTotal and SwapTotal, wich I found with 'awk'. At first I thought SwapTotal had no value, and I tested fot that, first on '10.1' and then again on 10.2'. SwapTotal was empty! Then: if SwapTotal had no value, SWAPTOTAL should be '0' (zero). Even then the summation reported an error. Then, I catched (not touch!) /proc/meminfo to my home directory ON 10.1. EMPTY! NOTHING! NIENTE! Summation of MEMTOT and SWAPTOT starts with analysing of the existance of /proc/meminfo but not for testing it was empty. Testing for that worked very well! Finally I could start up OpenSUSE 10.2 for the first time. BTW: I didn't mount or unmout procfs. If the system does mount yes or no at the right time, I cant see. /var/log/boot.msg is not yet written to disk at the time of error. I am not an programming expert and shall never be. Be happy with my report and keep on with puzzling problems like this. I you find the final solution please pass that one also to me. Merry Xmas and a happy new year. Henk Weebers -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 garloff@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |werner@novell.com ------- Comment #5 from garloff@novell.com 2006-12-22 05:43 MST ------- Suggested implementation. Werner, does this pass your review? if test -r /proc/meminfo -a -r /etc/sysconfig/ulimit; then # Get memory & swap sizes to evaluate the percentages MEMTOT=524288; SWPTOT=0 while read tag num unit; do case $tag in MemTotal:) MEMTOT=$num ;; SwapTotal:) SWPTOT=$num ;; esac done < /proc/meminfo TOT=$(($MEMTOT+$SWPTOT)) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 ------- Comment #6 from garloff@novell.com 2006-12-22 05:50 MST ------- Maybe even better: TOT=0 if test -r /proc/meminfo -a -r /etc/sysconfig/ulimit; then MEMTOT=0: SWPTOT=0 while read ... [...] TOT=$(($MEMTOT+$SWPTOT)) fi if test $TOT != 0; then unset NEW268LOCKLIMIT [...] fi So rather than assuming a default value of 512MB RAM and no swap, we just don't do any mem related ulimit settings in case we can't determine the real values for whatever reason (and I'm still confused about the reason). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 ------- Comment #7 from h.weebers@kpnplanet.nl 2007-01-02 14:25 MST ------- I had not yet time to implement your suggestion. Meanwhile 10.2 is running! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 h.weebers@kpnplanet.nl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|werner@novell.com | ------- Comment #8 from h.weebers@kpnplanet.nl 2007-01-06 03:22 MST ------- Created an attachment (id=111721) --> (https://bugzilla.novell.com/attachment.cgi?id=111721&action=view) repair (?) for initscript Last night I tested the proposed changes. It was necessary to add a test on /proc/meminfo being not empty. I am wondering how this can be, but this happens. What I (also) experienced was next: 1. cat /proc/meminfo gives a content back to console 2. cp /proc/meminfo /root/Desktop/ gives an empty file! The value of MEMTOT must not be 0 (zero). therefore I added default values for MEMTOT and SWPTOT. I did not test numbers between 0 and default values. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 h.weebers@kpnplanet.nl changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #110033|0 |1 is obsolete| | Attachment #111721|0 |1 is obsolete| | ------- Comment #9 from h.weebers@kpnplanet.nl 2007-01-08 12:54 MST ------- Created an attachment (id=111902) --> (https://bugzilla.novell.com/attachment.cgi?id=111902&action=view) fool safe version of initscript I increased my skills in bash programming. Now I can present a fool safe initscript (except for dummy values!) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 h.weebers@kpnplanet.nl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #10 from h.weebers@kpnplanet.nl 2007-01-08 12:58 MST ------- bug status changed -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 garloff@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #11 from garloff@novell.com 2007-01-19 16:12 MST ------- Reopen -- we have not yet provided a bug fix as update. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 ------- Comment #12 from garloff@novell.com 2007-01-19 16:17 MST ------- Created an attachment (id=113998) --> (https://bugzilla.novell.com/attachment.cgi?id=113998&action=view) initscript Thanks for your initscript versions. Here's mine. I would appreciate if you can test it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 ------- Comment #13 from h.weebers@kpnplanet.nl 2007-01-20 05:26 MST ------- Kurt, Thanks for your intersts for my script. Your versien was actualy my starting point. When SwapTotal gets an empty string, totalazing tot TOT doesn't work. I asked me the question: "Why is SapTotal empty?" Possibilities: 1. /proc/meminfo doesn't exist 2. /proc/meminfo is an empty file 3. /proc/meminfo doesn't contain values Well, /proc/meminfo is shown with the command 'ls -l'. It shows me always to be a zero length file. So the first test is always true. but is it usefull? In my opinion not because /proc/meminfo exists and /etc/sysconfig/ulimit exists. In fact /proc/meminfo is a virtual file and is not written to disk. Is it realy empty or does it not contail values? 'ls -l' cats data from disk and cat /proc/meminfo cats data from virtual file. If /proc/meminfo is not empty it should start with "Mem". The next field should contain a number and the third field indicates the units. What is written in /proc/meminfo for each value $num in each record? Is it an emty string or does it realy contain digits? I tested the script and found that the content of $num equals the string "kB" the first time initscript was running. So, no value! I realy wonder why /proc/meminfo behaves like I found. I would expect /proc/meminfo is initiated WITH values earlier in the start up procedure like you do. You agree? Can you tel me more ablout this? BTW: I tested MEMTOT=0. That did not work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Critical ------- Comment #14 from aj@novell.com 2007-02-01 06:03 MST ------- This does not look like a blocker. Kurt, do we have to release an update for this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=227742 ------- Comment #16 from h.weebers@kpnplanet.nl 2007-02-24 04:08 MST ------- Hi, A second PC was broken at the same way. This one I updated from SuSE linux 10.0 to opensuse 10.2. Here also an error occured while SWPTOT was empty or zero. Modification of initscript couldn't prevent hanging of the system after reaching level 5. /proc/meminfo is not proper filled with data. I bought the shop version of Novell Linux 10.2. The upgrade did not improve the functioning of the system. But then a new installation worked fine without initscript modifications. Could it be that some files are copied during an installation but nut during an upgrade? Regards, Henk Weebers -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com