open your file /etc/init.d/zenloadbalancer file

search this section (line 141):


#####
#running GUI
if( $pid=fork )
        {
        #$SIG{'CHLD'}='IGNORE';
       #print "Proceso de restart lanzado ...";
        }
elsif(defined $pid)
        {
        #$SIG{'CHLD'}=\&REAPER;
        #child
        #exec $MIGRASCRIPT,@args;
        system("/etc/init.d/minihttpd start > /dev/null &");
        exit(0);
        }


modify the lines with some like this:

#####
#running GUI
#if( $pid=fork )
#        {
        #$SIG{'CHLD'}='IGNORE';
       #print "Proceso de restart lanzado ...";
#        }
#elsif(defined $pid)
 #       {
        #$SIG{'CHLD'}=\&REAPER;
        #child
        #exec $MIGRASCRIPT,@args;
 #       system("/etc/init.d/minihttpd start > /dev/null &");
 #       exit(0);
 #      }
 system("/etc/init.d/minihttpd start > /dev/null &");


I can't understand why the original lines don't work for you. With
this configuration you could be problems, the start proccess on zen
would end never, but try and tell us

are you using zen load balancer v1rc3?


2011/6/16 Chiesa Stefano <[email protected]>:
> I tried again to restart the server and again the mini_httpd didn't start.
>
> How can I config the system to make it start automatically?
> (as you can see I'm not too good with linux)
>
> Thanks.
> Stefano.
>
> -----Messaggio originale-----
> Da: Chiesa Stefano [mailto:[email protected]]
> Inviato: giovedì 16 giugno 2011 15.20
> A: [email protected]
> Oggetto: [Zenloadbalancer-support] R: Restart web gui
>
> Ciao Emilio.
> Thanks a lot for your fast answer.
> After stop and start the web gui works fine.
>
> The question now is: why, as I rebooted the server, mini_httpd didn't restart?
>
> Thanks again.
>
> Stefano.
>
> root@s-dr-zen:~# netstat -a -n
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address           Foreign Address         State
> tcp        0      0 10.39.18.103:80         0.0.0.0:*               LISTEN
> tcp        0      0 10.39.18.100:80         0.0.0.0:*               LISTEN
> tcp        0      0 10.39.18.106:80         0.0.0.0:*               LISTEN
> tcp        0      0 127.0.0.1:14706         0.0.0.0:*               LISTEN
> tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
> -------
> tcp        0      0 10.39.19.110:444        0.0.0.0:*               LISTEN
> -------
> tcp        0      0 127.0.0.1:11717         0.0.0.0:*               LISTEN
> tcp        0      0 127.0.0.1:17030         0.0.0.0:*               LISTEN
> tcp        0      0 10.39.19.110:22         10.39.160.41:3710       
> ESTABLISHED
> tcp6       0      0 :::22                   :::*                    LISTEN
>
>
> root@s-dr-zen:~# ps -ef | grep httpd
> root      1995     1  0 15:11 ?        00:00:00 
> /usr/local/zenloadbalancer/app/mini_httpd/mini_httpd -C 
> /usr/local/zenloadbalancer/app/mini_httpd/mini_httpd.conf
>
>
> -----Messaggio originale-----
> Da: Emilio Campos [mailto:[email protected]]
> Inviato: giovedì 16 giugno 2011 15.10
> A: [email protected]
> Oggetto: Re: [Zenloadbalancer-support] Restart web gui
>
> /etc/init.d/minihttpd stop
> /etc/init.d/minihttpd start
>
> if your web gui cant' run you can send us your configuration file on:
>
> /usr/local/zenloadbalancer/app/mini_httpd/mini_httpd.conf
>
> this is should be the default configuration
>
> host=*
> port=444
> cgipat=**.cgi
> user=root
> logfile=/usr/local/zenloadbalancer/logs/mini_httpd.log
> pidfile=/var/run/mini_httpd.pid
> dir=/usr/local/zenloadbalancer/www
> ssl
> certfile=/usr/local/zenloadbalancer/app/mini_httpd/zenguicert.pem
> max_age=0
>
>
> Please tell me about your problem, it is interesting for me
>
>
> 2011/6/16 Chiesa Stefano <[email protected]>:
>> Hello Emilio.
>> Yestarday we powered off the zenn server in order to install a
>> 4-ethernet pci board. Everything went well (the system sees the 4 added
>> interfaces).
>>
>> But today I've discovered that the web gui isn't reachable any more.
>> I checked the "listening process" but no one listen on port 444
>>
>> Can you tell me the command to start the web gui? Or what can I do to
>> solve this problem?
>>
>>
>> root@s-dr-zen:/# netstat -a
>> Active Internet connections (servers and established)
>> Proto Recv-Q Send-Q Local Address           Foreign Address
>> State
>> tcp        0      0 10.39.18.103:www        *:*
>> LISTEN
>> tcp        0      0 10.39.18.100:www        *:*
>> LISTEN
>> tcp        0      0 10.39.18.106:www        *:*
>> LISTEN
>> tcp        0      0 localhost:14706         *:*
>> LISTEN
>> tcp        0      0 *:ssh                   *:*
>> LISTEN
>> tcp        0      0 localhost:11717         *:*
>> LISTEN
>> tcp        0      0 localhost:17030         *:*
>> LISTEN
>> tcp        0      0 10.39.19.110:ssh        s-chiesa.milano.wk:1874
>> ESTABLISHED
>> tcp6       0      0 [::]:ssh                [::]:*
>> LISTEN
>>
>>
>>
>> root@s-dr-zen:/# ps -ef
>> UID        PID  PPID  C STIME TTY          TIME CMD
>> root         1     0  0 14:10 ?        00:00:01 init [2]
>> root         2     0  0 14:10 ?        00:00:00 [kthreadd]
>> root         3     2  0 14:10 ?        00:00:00 [migration/0]
>> root         4     2  0 14:10 ?        00:00:00 [ksoftirqd/0]
>> root         5     2  0 14:10 ?        00:00:00 [watchdog/0]
>> root         6     2  0 14:10 ?        00:00:00 [migration/1]
>> root         7     2  0 14:10 ?        00:00:00 [ksoftirqd/1]
>> root         8     2  0 14:10 ?        00:00:00 [watchdog/1]
>> root         9     2  0 14:10 ?        00:00:00 [migration/2]
>> root        10     2  0 14:10 ?        00:00:00 [ksoftirqd/2]
>> root        11     2  0 14:10 ?        00:00:00 [watchdog/2]
>> root        12     2  0 14:10 ?        00:00:00 [migration/3]
>> root        13     2  0 14:10 ?        00:00:00 [ksoftirqd/3]
>> root        14     2  0 14:10 ?        00:00:00 [watchdog/3]
>> root        15     2  0 14:10 ?        00:00:00 [events/0]
>> root        16     2  0 14:10 ?        00:00:00 [events/1]
>> root        17     2  0 14:10 ?        00:00:00 [events/2]
>> root        18     2  0 14:10 ?        00:00:00 [events/3]
>> root        19     2  0 14:10 ?        00:00:00 [cpuset]
>> root        20     2  0 14:10 ?        00:00:00 [khelper]
>> root        21     2  0 14:10 ?        00:00:00 [netns]
>> root        22     2  0 14:10 ?        00:00:00 [async/mgr]
>> root        23     2  0 14:10 ?        00:00:00 [pm]
>> root        24     2  0 14:10 ?        00:00:00 [sync_supers]
>> root        25     2  0 14:10 ?        00:00:00 [bdi-default]
>> root        26     2  0 14:10 ?        00:00:00 [kintegrityd/0]
>> root        27     2  0 14:10 ?        00:00:00 [kintegrityd/1]
>> root        28     2  0 14:10 ?        00:00:00 [kintegrityd/2]
>> root        29     2  0 14:10 ?        00:00:00 [kintegrityd/3]
>> root        30     2  0 14:10 ?        00:00:00 [kblockd/0]
>> root        31     2  0 14:10 ?        00:00:00 [kblockd/1]
>> root        32     2  0 14:10 ?        00:00:00 [kblockd/2]
>> root        33     2  0 14:10 ?        00:00:00 [kblockd/3]
>> root        34     2  0 14:10 ?        00:00:00 [kacpid]
>> root        35     2  0 14:10 ?        00:00:00 [kacpi_notify]
>> root        36     2  0 14:10 ?        00:00:00 [kacpi_hotplug]
>> root        37     2  0 14:10 ?        00:00:00 [kseriod]
>> root        42     2  0 14:10 ?        00:00:00 [kondemand/0]
>> root        43     2  0 14:10 ?        00:00:00 [kondemand/1]
>> root        44     2  0 14:10 ?        00:00:00 [kondemand/2]
>> root        45     2  0 14:10 ?        00:00:00 [kondemand/3]
>> root        46     2  0 14:10 ?        00:00:00 [khungtaskd]
>> root        47     2  0 14:10 ?        00:00:00 [kswapd0]
>> root        48     2  0 14:10 ?        00:00:00 [ksmd]
>> root        49     2  0 14:10 ?        00:00:00 [aio/0]
>> root        50     2  0 14:10 ?        00:00:00 [aio/1]
>> root        51     2  0 14:10 ?        00:00:00 [aio/2]
>> root        52     2  0 14:10 ?        00:00:00 [aio/3]
>> root        53     2  0 14:10 ?        00:00:00 [crypto/0]
>> root        54     2  0 14:10 ?        00:00:00 [crypto/1]
>> root        55     2  0 14:10 ?        00:00:00 [crypto/2]
>> root        56     2  0 14:10 ?        00:00:00 [crypto/3]
>> root       284     2  0 14:10 ?        00:00:00 [ksuspend_usbd]
>> root       285     2  0 14:10 ?        00:00:00 [khubd]
>> root       289     2  0 14:10 ?        00:00:00 [ata/0]
>> root       290     2  0 14:10 ?        00:00:00 [ata/1]
>> root       291     2  0 14:10 ?        00:00:00 [ata/2]
>> root       292     2  0 14:10 ?        00:00:00 [ata/3]
>> root       293     2  0 14:10 ?        00:00:00 [ata_aux]
>> root       294     2  0 14:10 ?        00:00:00 [cciss_scan]
>> root       295     2  0 14:10 ?        00:00:00 [scsi_eh_0]
>> root       296     2  0 14:10 ?        00:00:00 [scsi_eh_1]
>> root       337     2  0 14:10 ?        00:00:00 [usbhid_resumer]
>> root       375     2  0 14:10 ?        00:00:00 [kjournald]
>> root       482     1  0 14:10 ?        00:00:00 udevd --daemon
>> root       636   482  0 14:10 ?        00:00:00 udevd --daemon
>> root       637   482  0 14:10 ?        00:00:00 udevd --daemon
>> root       687     2  0 14:10 ?        00:00:00 [kpsmoused]
>> root       793     2  0 14:10 ?        00:00:00 [edac-poller]
>> root       818     2  0 14:10 ?        00:00:01 [kipmi0]
>> root       892     2  0 14:10 ?        00:00:00 [flush-104:0]
>> root       989     2  0 14:10 ?        00:00:00 [kjournald]
>> root       990     2  0 14:10 ?        00:00:00 [kjournald]
>> root       991     2  0 14:10 ?        00:00:00 [kjournald]
>> root      1010     2  0 14:10 ?        00:00:00 [kjournald]
>> root      1186     1  0 14:10 ?        00:00:00 /usr/sbin/rsyslogd -c4
>> root      1230     1  0 14:10 ?        00:00:00 /usr/sbin/acpid
>> root      1267     1  0 14:10 ?        00:00:00 /usr/sbin/cron
>> root      1273     1  0 14:10 ?        00:00:00 /usr/sbin/sshd
>> root      1302     1  0 14:10 ?        00:00:00
>> /usr/local/zenloadbalancer/app/pen/bin/pen -S 4 -c 2049 -x 1000 -F
>> /usr/local/zenloadbalancer/config/SR-Pluris_pe
>> root      1305     1  0 14:10 ?        00:00:00
>> /usr/local/zenloadbalancer/app/pen/bin/pen -S 4 -c 50 -x 1000 -F
>> /usr/local/zenloadbalancer/config/SR-Ipsoa_pen.c
>> root      1308     1  0 14:10 ?        00:00:00
>> /usr/local/zenloadbalancer/app/pen/bin/pen -S 4 -c 50 -x 1000 -F
>> /usr/local/zenloadbalancer/config/SR-Leggi_pen.c
>> root      1320     1  0 14:10 tty1     00:00:00 /sbin/getty 38400 tty1
>> root      1321     1  0 14:10 tty2     00:00:00 /sbin/getty 38400 tty2
>> root      1322     1  0 14:10 tty3     00:00:00 /sbin/getty 38400 tty3
>> root      1323     1  0 14:10 tty4     00:00:00 /sbin/getty 38400 tty4
>> root      1324     1  0 14:10 tty5     00:00:00 /sbin/getty 38400 tty5
>> root      1325     1  0 14:10 tty6     00:00:00 /sbin/getty 38400 tty6
>> root      1348  1273  0 14:12 ?        00:00:00 sshd: root@pts/0
>> root      1350  1348  0 14:12 pts/0    00:00:00 -bash
>> root      1618  1350  0 14:37 pts/0    00:00:00 ps -ef
>>
>>
>>
>> eth0      Link encap:Ethernet  HWaddr 00:1b:78:92:96:c2
>>          inet addr:10.39.18.110  Bcast:10.39.19.255  Mask:255.255.254.0
>>          inet6 addr: fe80::21b:78ff:fe92:96c2/64 Scope:Link
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          RX packets:11369 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:6248 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:7126043 (6.7 MiB)  TX bytes:5625730 (5.3 MiB)
>>          Interrupt:16 Memory:f8000000-f8012800
>>
>> eth0:1    Link encap:Ethernet  HWaddr 00:1b:78:92:96:c2
>>          inet addr:10.39.18.100  Bcast:10.39.19.255  Mask:255.255.254.0
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          Interrupt:16 Memory:f8000000-f8012800
>>
>> eth0:2    Link encap:Ethernet  HWaddr 00:1b:78:92:96:c2
>>          inet addr:10.39.18.103  Bcast:10.39.19.255  Mask:255.255.254.0
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          Interrupt:16 Memory:f8000000-f8012800
>>
>> eth0:3    Link encap:Ethernet  HWaddr 00:1b:78:92:96:c2
>>          inet addr:10.39.18.106  Bcast:10.39.19.255  Mask:255.255.254.0
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          Interrupt:16 Memory:f8000000-f8012800
>>
>> eth1      Link encap:Ethernet  HWaddr 00:1b:78:92:96:c0
>>          inet addr:10.39.19.110  Bcast:10.39.19.255  Mask:255.255.254.0
>>          inet6 addr: fe80::21b:78ff:fe92:96c0/64 Scope:Link
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          RX packets:8531 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:6926686 (6.6 MiB)  TX bytes:1516 (1.4 KiB)
>>          Interrupt:17 Memory:fa000000-fa012800
>>
>> eth2      Link encap:Ethernet  HWaddr 00:26:55:db:68:3c
>>          BROADCAST MULTICAST  MTU:1500  Metric:1
>>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>          Memory:fdbe0000-fdc00000
>>
>> eth3      Link encap:Ethernet  HWaddr 00:26:55:db:68:3d
>>          BROADCAST MULTICAST  MTU:1500  Metric:1
>>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>          Memory:fdce0000-fdd00000
>>
>> eth4      Link encap:Ethernet  HWaddr 00:26:55:db:68:3f
>>          BROADCAST MULTICAST  MTU:1500  Metric:1
>>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>          Memory:fdee0000-fdf00000
>>
>> eth5      Link encap:Ethernet  HWaddr 00:26:55:db:68:3e
>>          BROADCAST MULTICAST  MTU:1500  Metric:1
>>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>          Memory:fdde0000-fde00000
>>
>> lo        Link encap:Local Loopback
>>          inet addr:127.0.0.1  Mask:255.0.0.0
>>          inet6 addr: ::1/128 Scope:Host
>>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:0
>>          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>
>>
>> ----------------------------------------
>> Stefano Chiesa
>> Wolters Kluwer Italia
>> Strada 1, Palazzo F6
>> 20090 Milanofiori Assago (Mi) - Italia
>> Phone +39 0282476279 (20279 Voip)
>> Fax +39 0282476633
>>
>>
>> ------------------------------------------------------------------------------
>> EditLive Enterprise is the world's most technically advanced content
>> authoring tool. Experience the power of Track Changes, Inline Image
>> Editing and ensure content is compliant with Accessibility Checking.
>> http://p.sf.net/sfu/ephox-dev2dev
>> _______________________________________________
>> Zenloadbalancer-support mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>>
>
>
>
> --
> Load balancer distribution - Open Source Project
> http://zenloadbalancer.sourceforge.net
> Distribution list (subscribe): [email protected]
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Zenloadbalancer-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Zenloadbalancer-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Zenloadbalancer-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>



-- 
Load balancer distribution - Open Source Project
http://zenloadbalancer.sourceforge.net
Distribution list (subscribe): [email protected]

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Zenloadbalancer-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support

Reply via email to