Attachment 144450 Details for Bug 191279 – More comprehensive test cases & results

More comprehensive test cases & results

testing-details.txt (text/plain), 4.45 KB, created by dreamcat4 on 2014-07-06 10:35:04 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: dreamcat4

Created: 2014-07-06 10:35:04 UTC

Size: 4.45 KB

patch

obsolete

>Today I have tried:
>
>* renaming the jail 'zabbix' --> 'a-zabbix', so that it is first jail in the qjail's list of jails to be started. Result: fail.
>* putting all other jails into manual mode (so they won't be started at boot time) *except* for the jail 'zabbix'. Result: fail.
>* enabled 'allow.sysvipc' setting in the previous jail before zabbix also. So to find out if it can be any various 2nd, 3rd jail being started with sysvipc to work. Or must be the same partucular jail started twice? Result: fail.
>
>freenas // root^> jls -h -j webcamd allow.sysvipc
>allow.sysvipc
>0
>freenas // root^> jls -h -j zabbix allow.sysvipc
>allow.sysvipc
>0
>freenas // root^> jls -h -j webcamd allow.sysvipc
>allow.sysvipc
>0
>freenas // root^> jls -h -j zabbix allow.sysvipc
>allow.sysvipc
>0
>freenas // root^> qjail restart webcamd zabbix
>Jail successfully stopped  webcamd
>Jail successfully started  webcamd
>Jail successfully stopped  zabbix
>Jail successfully started  zabbix
>freenas // root^> jls -h -j webcamd allow.sysvipc
>allow.sysvipc
>1
>freenas // root^> jls -h -j zabbix allow.sysvipc
>allow.sysvipc
>1
>
>Conclusion so far: So at this point, we can see it affect each jails individually. And the startup order / in conjunction with other jails at boot time make no difference. The zabbix software is also proved not to be involved whatsoever, since the problem occurs equally also for 'webcamd' jail, which has no sysvipc software inside it (just only changed the jail flag).
>
>New test:
>
>* Don't start the sysvipc jails at boot time. Start them manually (1st time), but waiting a couple of minutes after full system bootup has completed. Result: not testable due to some unrelated bug with manual mode, that when set the jail would not even started manually.
>
>FYI - enabling manual mode also has another anwanted effect: of disabling the "allow.sysvipc" option in qjail's saved definition files. However that is not the bug not being tested here. So we avoid confusing the 2 issue by excluding the use of qjail's 'manual mode' completely from this PR's testing.
>
>Disable manual mode
>
>freenas // root^> qjail config -M zabbix
>Successful set manual status off zabbix
>freenas // root^> qjail config -M webcamd
>Successful set manual status off webcamd
>freenas // root^> sysrc -x qjail_enable        
>
>Re-enable the sysvipc setting (which was incorrectly disabled by manual mode bug).
>
>freenas // root^> qjail config -y webcamd
>Successfully enabled allow.sysvipc for webcamd
>freenas // root^> qjail config -y zabbix 
>Successfully enabled allow.sysvipc for zabbix
>
>* Don't start the qjail service at boot time. (to avoid manual mode bug). Start jails manually (1st time), but waiting a couple of minutes after full system bootup has completed. Result: success! sysvipc works first go.
>
>freenas // root^> sysrc qjail_enable=NO
>qjail_enable:  -> NO
>freenas // root^> reboot
>
># ... wait for reboot, log back in again
>freenas // root^> qjail start webcamd
>Jail successfully started  webcamd
>freenas // root^> jls -h -j webcamd allow.sysvipc
>allow.sysvipc
>1
>freenas // root^> 
>
>Now we are getting somewhere.
>
>Possibility #1: There is either something still happening (system-wise) during overall boot, which is resolved after the host machine's bootup sequence completed.
>OR
>Possibility #2: The rc.d script of qjail, named 'qjail.bootime' is doing something differently than when we start each jails individually on the command line. And whatever that difference results in this strange bug occuring / not occuring.
>
>New test:
>
>* Don't start the qjail service at boot time. (to avoid manual mode bug). Wait a couple of minutes after full system bootup has completed. Then start the jails through qjail's rc.d script this time (rather than previous success case, which was to manually start an individual jail with 'qjail start'). Result: fail.
>
>freenas // root^> sysrc qjail_enable
>qjail_enable: NO
>freenas // root^> reboot
>
># ... wait for reboot, log back in again
>freenas // root^> sysrc qjail_enable=YES
>qjail_enable: NO -> YES
>freenas // root^> service qjail.bootime start
>freenas // root^> jls -h -j webcamd allow.sysvipc
>allow.sysvipc
>0
>
>Conclusion: The problem is not related to general bootup issue. But it is something specific happening in terms of qjail's rc.d startup. may or may not be due the 'qjail.bootime' rc.d script itself. It could equally be something amiss within the shell environment the rc.d script is being executed in. For example: the $PATH environment variable given to an rc.d script (by default) will be missing '/usr/local/bin' and '/usr/local/sbin'.
>

Actions: View

Attachments on bug 191279: 144450 | 144452 | 144453