2016-05-17 16:30 GMT+08:00 Fred Liu <fred.f...@gmail.com>: > 2016-05-17 15:41 GMT+08:00 Chris Ridd <chrisr...@mac.com>: >> >>> On 17 May 2016, at 08:25, Fred Liu <fred.f...@gmail.com> wrote: >>> >>> 2016-05-17 15:10 GMT+08:00 Chris Ridd <chrisr...@mac.com>: >>>> >>>>> On 17 May 2016, at 07:40, Fred Liu <fred.f...@gmail.com> wrote: >>>>> >>>>> 2016-05-17 14:32 GMT+08:00 Joshua M. Clulow <j...@sysmgr.org>: >>>>>> On 16 May 2016 at 23:29, Fred Liu <fred.f...@gmail.com> wrote: >>>>>>> I have no success to boot the system V init scripts. >>>>>>> Any success here? >>>>>> >>>>>> Can you give us a bit more detail about what you're doing? Is this a >>>>>> custom script you have added to your machine? Is it in the global >>>>>> zone of your SmartOS host, or in a SmartOS or LX-branded zone? At >>>>>> what path did you install the file? >>>>>> >>>>>> >>>>>> Cheers. >>>>>> >>>>> >>>>> We are running (CentOS 6.7 20151005) LX Brand. It is a custom script. >>>>> I installed it on /etc/init.d/iqs. It is just a simple sh script: >>>> >>>> Add “set -x” near the start of the script and find out where it is failing. >>>> >>> >>> It can be started manually with no problems. >>> The issue it can't be automatically started when we reboot LX Brand. >>> Because the boot process is totally different in LX Brand. >>> So the question converts to how to debug the boot process in LX Brand. >> >> OK, that’s some useful extra detail. Does something even *try* to run your >> script? Have you used chkconfig to enable it for the right Linux run levels? >> Maybe the LX zone isn’t in the run level you think it is. >> >> I would have thought that set -x could still be helpful if the output is >> captured in a system log which you can look at later. (I don’t recall what >> Linux does.) Or echo something into a tmp file, and see if that gets written >> during the boot. >> > > Added "-x" and rebooted. > /var/log/message: > > May 17 16:26:56 sha01 init: tty (console) main process (3698) killed > by TERM signal > May 17 16:26:57 sha01 xinetd[3549]: Exiting... > May 17 16:27:19 sha01 rpcbind: rpcbind terminating on signal. Restart > with "rpcbind -w" > May 17 16:27:20 sha01 kernel: Kernel logging (proc) stopped. > May 17 16:27:20 sha01 rsyslogd: [origin software="rsyslogd" > swVersion="5.8.10" x-pid="3374" x-info="http://www.rsyslog.com";] > exiting on signal 15. > May 17 16:27:26 sha01 kernel: imklog 5.8.10, log source = /proc/kmsg started. > May 17 16:27:26 sha01 rsyslogd: [origin software="rsyslogd" > swVersion="5.8.10" x-pid="4476" x-info="http://www.rsyslog.com";] start > May 17 16:27:26 sha01 rpc.statd[4520]: Version 1.2.3 starting > May 17 16:27:26 sha01 sm-notify[4521]: Version 1.2.3 starting > May 17 16:27:26 sha01 ypbind[4566]: Connection to D-BUS system message > bus failed: Failed to connect to socket > /var/run/dbus/system_bus_socket: No such file or directory. > May 17 16:27:28 sha01 ypbind: NIS domain: issish, NIS server: cn07 > May 17 16:27:30 sha01 xinetd[4675]: xinetd Version 2.3.14 started with > libwrap loadavg labeled-networking options compiled in. > May 17 16:27:30 sha01 xinetd[4675]: Started working: 1 available service > > Seems nothing special. > > Thanks. >
After 2-3 minutes, it finally works! I am sure it is related to the issue that there is a lag on the very first try to mount nfs v3 path in Linux Brand. Anyway, many thanks for your nice help!! Fred ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
