Warnings thrown when booting MK after merging pull request #60 #61

Closed
tjmcs opened this Issue Feb 12, 2013 · 1 comment

Comments

Projects
None yet
2 participants
@tjmcs

tjmcs commented Feb 12, 2013

After the recent changes made when pull request #60 was merged, there are now two warnings thrown during the Microkernel boot process that were not thrown previously. Specifically, the Microkernel Controller is not parsing the gem list that it receives back from the local mirror correctly and it is trying to install two "non-existent gems" with the names >= and 1.7.7. Here's a snippet taken from an SSH session that shows those two errors (as they appear in the /tmp/rz_mk_control_server.rb.output file in a debug instance of the latest Microkernel that was used to boot a VMware Fusion VM):

# ssh tc@192.168.78.73
tc@192.168.78.73's password: 
 (?- 
 //\   Core is distributed with ABSOLUTELY NO WARRANTY.
 v_/_           www.tinycorelinux.com

tc@mk000C29E8B0B6:~$ cat /tmp/rz_mk_control_server.rb.output 
rz_mk_control_server.rb: process with pid 1659 started.
/usr/local/lib/ruby/1.8/razor_microkernel/rz_mk_registration_manager.rb:16: warning: already initialized constant RZ_MK_LOG_PATH
/usr/local/lib/ruby/1.8/razor_microkernel/rz_mk_kernel_module_manager.rb:25: warning: already initialized constant RZ_MK_LOG_PATH
/usr/local/bin/rz_mk_control_server.rb:141: warning: already initialized constant RZ_MK_LOG_PATH
WARNING; gem '>=' is not available from the named mirror (http://localhost:2158/gem-mirror)
WARNING; gem '1.7.7' is not available from the named mirror (http://localhost:2158/gem-mirror)
/usr/bin/tce-load: line 189: can't create /tmp/appserr: Permission denied
Connecting to localhost:2157 (127.0.0.1:2157)
libdnet.tcz          100% |*******************************| 86016   0:00:00 ETA
Connecting to localhost:2157 (127.0.0.1:2157)
ncurses-common.tcz   100% |*******************************| 12288   0:00:00 ETA
Connecting to localhost:2157 (127.0.0.1:2157)
ncurses.tcz          100% |*******************************|   148k  0:00:00 ETA
Connecting to localhost:2157 (127.0.0.1:2157)
procps.tcz           100% |*******************************|   140k  0:00:00 ETA
--- %< output truncated here >% ---
tc@mk000C29E8B0B6:~$ 

(note; I truncated the output of the cat command shown above for brevity). The two warnings shown in that snippet are, no doubt, due to the recent changes that were made to the /tmp/gem-mirror/gems/gem.list file as part of pull request #60, the results of which can be seen in this snippet from that same SSH session:

tc@mk000C29E8B0B6:~$ cat /tmp/gem-mirror/gems/gem.list 
stomp
facter
json_pure  >= 1.7.7
daemons
tc@mk000C29E8B0B6:~$

Obviously, this file is not being parsed correctly by the Microkernel Controller (which is not surprising considering that this file was assumed to be a simple list of gems, not a list of gems that includes information like limits on the version numbers that should be installed)...

While the errors thrown are mostly harmless (the gem the user wanted to install during the boot process, the json_pure gem, is installed, and the correct version, v1.7.7, is installed since that is the version that was downloaded and included in the local mirror), we should really try to resolve this issue in order to remove these spurious errors from the output that appears on the console during the boot process. We also should ensure that the correction version will always be downloaded and included in the bundle file that is being built (since that is the only version that the local mirror will make available during the Microkernel boot process). That means that the local mirror must always include the correct versions of these gems, so new versions of these gems may have to be downloaded and included in the bundle file (even if the -r or --reuse-prev-dl flag were set when the build-bundle-file.sh script was invoked).

@slippycheeze

This comment has been minimized.

Show comment Hide comment
@slippycheeze

slippycheeze Feb 12, 2013

Contributor

After the recent changes made when pull request #60 was merged, there are
now two warnings thrown during the Microkernel boot process that were not
thrown previously.

Gosh. If only we had some actual tests to verify that the code we run
in the Microkernel actually functioned, this wouldn't be nearly as
much guesswork every time a change was made. As it is, you are right
and this is broker be the change to the gem list used in mirroring.

While the errors thrown are mostly harmless (the gem the user wanted to
install during the boot process, the json_pure gem, is installed, and the
correct version, v1.7.7, is installed since that is the version that was
downloaded and included in the local mirror), we should really try to
resolve this issue in order to remove these spurious errors from the output
that appears on the console during the boot process.

Yep. Having errors during the install process is definitely a
problem. Thankfully the system still works after that.

Contributor

slippycheeze commented Feb 12, 2013

After the recent changes made when pull request #60 was merged, there are
now two warnings thrown during the Microkernel boot process that were not
thrown previously.

Gosh. If only we had some actual tests to verify that the code we run
in the Microkernel actually functioned, this wouldn't be nearly as
much guesswork every time a change was made. As it is, you are right
and this is broker be the change to the gem list used in mirroring.

While the errors thrown are mostly harmless (the gem the user wanted to
install during the boot process, the json_pure gem, is installed, and the
correct version, v1.7.7, is installed since that is the version that was
downloaded and included in the local mirror), we should really try to
resolve this issue in order to remove these spurious errors from the output
that appears on the console during the boot process.

Yep. Having errors during the install process is definitely a
problem. Thankfully the system still works after that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment