web interface management

dommy · 26-07-2008, 08:27 PM

Hello,

for a big mistake

I have stopped the web gui interface, now I am not able to connect to the nas for management purpose, I suppose that in some way will be still possible to restart the web gui, can someone help me? I am still able to login to the Nas by the way of telnet.
Thanks to all in advance
Dommy

dommy · 27-07-2008, 07:33 AM

Hello,

Originally Posted by dommy

Hello,

for a big mistake I have stopped the web gui interface, now I am not able to connect to the nas for management purpose, I suppose that in some way will be still possible to restart the web gui, can someone help me? I am still able to login to the Nas by the way of telnet.
Thanks to all in advance
Dommy

Can anyone help?

I am really in a mess.........

Cheers

Funkstar · 27-07-2008, 08:21 AM

Might be an idea to tell us what Thecus NAS you have

dommy · 27-07-2008, 08:32 AM

Hello,

Originally Posted by Funkstar

Might be an idea to tell us what Thecus NAS you have

You are right, sorry,

the raid is a 5200 PRO.

Tnx
Dommy

fruitflier · 27-07-2008, 07:56 PM

I had problem accessing the web server once. I reset the box to factory default and used the setup wizard to setup the connection. I could connect my N5200 again from web browser. Hope this help.

dommy · 28-07-2008, 06:44 AM

Hello,

Originally Posted by fruitflier

I had problem accessing the web server once. I reset the box to factory default and used the setup wizard to setup the connection. I could connect my N5200 again from web browser. Hope this help.

Tnx for to take time to answer, probably your suggestion will be right but in that case I will loose all the configuration.
There are a lot of folder and trustee configured and also users and groups and isn't so simple to recover all also due the fact that is impossible to save the configuration file.
I am not a linux expert but I am sure that there is the possibility to start all service by hands, I hope that someone expert put me in the correct way.
Cheers
Dommy

pit234a · 28-07-2008, 07:16 PM

Do you remember what you exactely did?

You have a chance at least to find what happens on your NAS in entering it via ssh connection, after you installed the according plugin (they don't name it plugin, I forgot, but you should find it mentioned here somewhere).

dommy · 28-07-2008, 09:20 PM

Originally Posted by pit234a

Do you remember what you exactely did?

You have a chance at least to find what happens on your NAS in entering it via ssh connection, after you installed the according plugin (they don't name it plugin, I forgot, but you should find it mentioned here somewhere).

I remember that I have disabled the web interface.
About the ssh connection I know that the connection work well, I am able to connect with userid and pwd to my nas with a telnet connection and I can see all the data and the file system, what I am looking for are the commands for to restart the web interface from telnet connection
Cheers

pit234a · 29-07-2008, 07:12 AM

so, I am no expert here.
I do not know what it means to disable the webif, it could cause a simple kill of the service that used to realize it, it could cause the webif to accept no one anymore or it could just stop listening of the port used for http, maybe somewhat more that I cannot see now.
I also do not know which command would start that service back, means in case it is not running at all. I know, how unix systems handle that usually: the service is called by an init script and the different stages of such scripts are in some files called rc1 to rc5 or rc6.
I find some here:

root@127.0.0.1:~# ls -l /etc/init.d/
-rwxr-xr-x 1 root root 36 Apr 5 22:20 ifplugd*
-rwxr-xr-x 1 root root 4394 Apr 5 22:20 rc.0*
-rwxr-xr-x 1 root root 425 Apr 5 22:20 rc.1*
-rwxr-xr-x 1 root root 1875 Apr 5 22:20 rc.2*
-rwxr-xr-x 1 root root 1368 Apr 5 22:20 rc.3*
lrwxrwxrwx 1 root root 4 Apr 5 22:20 rc.4 -> rc.2*
lrwxrwxrwx 1 root root 4 Apr 5 22:20 rc.5 -> rc.2*
lrwxrwxrwx 1 root root 4 Apr 5 22:20 rc.6 -> rc.0*
-rwxr-xr-x 1 root root 32 Apr 5 22:20 rc.local*
-rwxr-xr-x 1 root root 1094 Apr 5 22:20 rc.samba*
-rwxr-xr-x 1 root root 1249 Apr 5 22:20 rc.sshd*
-rwxr-xr-x 1 root root 2312 Apr 5 22:20 rc.sysinit*

There you would have to start your search and finding a passage that starts the webif part in one of those scripts.

Here, I show you the output of ps -w on my NAS. That gives all the processes currently running and almost ind the sequence, they had been started. Maybe, you find differences to yours.

root@127.0.0.1:~# ps -w
PID Uid VmSize Stat Command
1 root 244 S init
2 root SWN [ksoftirqd/0]
3 root SW< [events/0]
4 root SW< [khelper]
5 root SW< [kthread]
7 root SW< [kblockd/0]
10 root SW< [khubd]
61 root SW [pdflush]
62 root SW [pdflush]
64 root SW< [aio/0]
63 root SW [kswapd0]
650 root SW< [kseriod]
683 root SW< [eventsched/0]
985 root SW< [btn_sched/0]
1020 root 836 S /bin/sh /img/bin/mon_pwbtn.sh
1022 root 200 S cat /proc/thecus_event
1061 root SW [scsi_eh_0]
1062 root SW [scsi_eh_1]
1063 root SW [scsi_eh_2]
1064 root SW [scsi_eh_3]
1065 root SW [scsi_eh_4]
1066 root SW [scsi_eh_5]
1067 root SW [scsi_eh_6]
1068 root SW [scsi_eh_7]
2045 root SW [md0_raid1]
2048 root SW [md1_raid5]
2132 root SW [kjournald]
2144 root SW [kjournald]
2285 root 884 S /bin/sh /app/bin/raid_m2
2352 root 264 S /img/bin/udpr
2438 root 604 S /opt/apache/bin/httpd -k start -DSSL
2525 1 356 S /sbin/portmap
2587 root 608 S /opt/apache/bin/httpd -k start -DSSL
2588 root 612 S /opt/apache/bin/httpd -k start -DSSL
2589 root 608 S /opt/apache/bin/httpd -k start -DSSL
2635 root 564 S /opt/cups/sbin/cupsd
2664 root 600 S /opt/apache/bin/httpd -k start -DSSL
2665 root 616 S /opt/apache/bin/httpd -k start -DSSL
2737 root 336 S /usr/sbin/crond -L /dev/null
2833 root 364 S /opt/nfs-utils/sbin/rpc.rquotad
2835 root SW [nfsd]
2836 root SW [nfsd]
2837 root SW [nfsd]
2838 root SW [nfsd]
2839 root SW [nfsd]
2840 root SW [nfsd]
2841 root SW [nfsd]
2842 root SW [nfsd]
2843 root SW [lockd]
2844 root SW< [rpciod/0]
2846 root 724 S /opt/nfs-utils/sbin/rpc.mountd
2859 root 464 S /opt/nfs-utils/sbin/rpc.idmapd
2927 root 984 S /bin/sh /img/bin/check_raid_full.sh
2932 root 1164 S /bin/sh /img/bin/check_fan_lan.sh
2937 root 936 S /bin/sh /img/bin/mon_reset.sh
2952 root 228 S /sbin/getty 38400 tty1
2953 root 228 S /sbin/getty 38400 tty2
2959 root 228 S /sbin/getty 38400 tty3
2965 root 228 S /sbin/getty 38400 tty4
2971 root 228 S /sbin/getty 38400 tty5
3125 root 460 S /raid/data/module/SSHD/system/bin/sshd -f /raid/data/module/SSHD/system/etc/ssh/sshd_config
3721 root 448 S /opt/bin/iscsid
3722 root 2088 S < /opt/bin/iscsid
3983 root 500 S /opt/bin/ietd --config=/raid/sys/ietd.conf
3993 root 352 S ./pure-authd -p /var/run/pure-authd.pid -s /var/run/ftpd.sock -r /img/bin/ftp-auth-handler
3995 root 460 S pure-ftpd (SERVER)
4056 root 588 S /opt/bin/openvpn --dev tun --persist-tun --persist-key --proto tcp-server --keepalive 10 60 --verb 0 --wri
4058 root 352 S ./pure-authd -p /var/run/nsync-au.pid -s /var/run/nsync.sock -r /app/bin/ftp-auth-handler
4060 root 456 S pure-ftpd (SERVER)
4977 root 200 S cat /proc/thecus_eventc
7061 root 628 S /opt/apache/bin/httpd -k start -DSSL
11074 root 608 S /opt/apache/bin/httpd -k start -DSSL
3267 root 616 S /opt/apache/bin/httpd -k start -DSSL
23314 root 616 S /opt/apache/bin/httpd -k start -DSSL
7403 root 620 S /opt/apache/bin/httpd -k start -DSSL
15353 root 512 S /opt/netatalk/sbin/atalkd -f /etc/netatalk/atalkd.conf
16190 root 408 S /opt/netatalk/sbin/papd -f /etc/netatalk/papd.conf
16192 root 520 S /opt/netatalk/sbin/afpd -c 50 -U /etc/netatalk/uams -n N5200 -f /etc/netatalk/AppleVolumes.default -s /etc
16446 root 1820 S /img/bin/agent2
16447 root 1820 S /img/bin/agent2
16449 root 1820 S /img/bin/agent2
16450 root 1820 S /img/bin/agent2
16451 root 1820 S /img/bin/agent2
16452 root 1820 S /img/bin/agent2
9536 root 852 S sshd: sys@pts/0

Prior to that, I would check whether the service is still offered with the help of nmap from my PC, see this:

pit@syo ~:-> nmap -v 192.168.0.100

Starting Nmap 4.62 ( http://nmap.org ) at 2008-07-29 08:07 CEST
Initiating Ping Scan at 08:07
Scanning 192.168.0.100 [1 port]
Completed Ping Scan at 08:07, 0.00s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 08:07
Completed Parallel DNS resolution of 1 host. at 08:07, 0.06s elapsed
Initiating Connect Scan at 08:07
Scanning 192.168.0.100 [1715 ports]
Discovered open port 443/tcp on 192.168.0.100
Discovered open port 21/tcp on 192.168.0.100
Discovered open port 22/tcp on 192.168.0.100
Discovered open port 80/tcp on 192.168.0.100
Discovered open port 2049/tcp on 192.168.0.100
Discovered open port 631/tcp on 192.168.0.100
Discovered open port 2000/tcp on 192.168.0.100
Discovered open port 905/tcp on 192.168.0.100
Discovered open port 548/tcp on 192.168.0.100
Discovered open port 111/tcp on 192.168.0.100
Completed Connect Scan at 08:07, 0.05s elapsed (1715 total ports)
Host 192.168.0.100 appears to be up ... good.
Interesting ports on 192.168.0.100:
Not shown: 1705 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
80/tcp open http
111/tcp open rpcbind
443/tcp open https
548/tcp open afp
631/tcp open ipp
905/tcp open unknown
2000/tcp open callbook
2049/tcp open nfs

Read data files from: /usr/local/share/nmap
Nmap done: 1 IP address (1 host up) scanned in 0.185 seconds

So again: To disable the webif, can mean different things. It would be way better, to have an idea about what exactly disables it actually. Let's say: in case you changed something in the configuration that caused it to no longer accepting any login or that even causes the service to crash when it is started, it will not help to find the command to start that service, because it can only start the destroyed one.
Here, you would probably have to just eliminate the fault and restart the NAS.

Sorry, I cannot help with detailed information, because I don't have them. But maybe you get some new ideas by just discussing your problem.

edit: one hint: the service used for http in the NAS is apache

dommy · 29-07-2008, 07:39 AM

Hello,

Originally Posted by pit234a

so, I am no expert here.
I do not know what it means to disable the webif, it could cause a simple kill of the service that used to realize it, it could cause the webif to accept no one anymore or it could just stop listening of the port used for http, maybe somewhat more that I cannot see now.
I also do not know which command would start that service back, means in case it is not running at all. I know, how unix systems handle that usually: the service is called by an init script and the different stages of such scripts are in some files called rc1 to rc5 or rc6.
I find some here:

There you would have to start your search and finding a passage that starts the webif part in one of those scripts.

Here, I show you the output of ps -w on my NAS. That gives all the processes currently running and almost ind the sequence, they had been started. Maybe, you find differences to yours.

Prior to that, I would check whether the service is still offered with the help of nmap from my PC, see this:

So again: To disable the webif, can mean different things. It would be way better, to have an idea about what exactly disables it actually. Let's say: in case you changed something in the configuration that caused it to no longer accepting any login or that even causes the service to crash when it is started, it will not help to find the command to start that service, because it can only start the destroyed one.
Here, you would probably have to just eliminate the fault and restart the NAS.

Sorry, I cannot help with detailed information, because I don't have them. But maybe you get some new ideas by just discussing your problem.

edit: one hint: the service used for http in the NAS is apache

Thank you very much for your time and support.
I will try to make checks with the information that you have given me, I hope to be able to do something, unfortunately my job is totally different and I do not have any capacity in the Linux world to which I am really incompetent.
I try to better better what I had done:
In practice I connected to nas with a browser as usual to watch for a module, then, by mistake, instead of stopping the module used for to publish a web (the web server) I stopped the web interface of the nas....... that's all, after this is I am not able to connect the NAS by browser.
The only connection available is the sysuser installed.
I have activated a ticket with the Thecus Helpdesk two days ago, but seem that the Thecus people have more important things to do, probably the words "customer care" are insignificant for them,
perhaps know better the terms "business at any cost"

Thanks again for your support
Cheers
Dommy

nibbles · 29-07-2008, 09:30 PM

Originally Posted by dommy

Hello,

Thank you very much for your time and support.
I will try to make checks with the information that you have given me, I hope to be able to do something, unfortunately my job is totally different and I do not have any capacity in the Linux world to which I am really incompetent.
I try to better better what I had done:
In practice I connected to nas with a browser as usual to watch for a module, then, by mistake, instead of stopping the module used for to publish a web (the web server) I stopped the web interface of the nas....... that's all, after this is I am not able to connect the NAS by browser.
The only connection available is the sysuser installed.
I have activated a ticket with the Thecus Helpdesk two days ago, but seem that the Thecus people have more important things to do, probably the words "customer care" are insignificant for them,
perhaps know better the terms "business at any cost"

Thanks again for your support
Cheers
Dommy

Hello Dommy,

Something tells me from reading this, maybe you were looking at a particular howto in regards to trying to setup the N5200 to run a basic website. (just a hunch) however, I remember coming across something about this and I think you might be able to re-enable it via ssh. I am not about to test it on my own box (since I don't need httpd daemon working for this purpose)

I remember reading some notes about this part and will see if there's a way to re-enable it from command level. It might take me a few days since I'm currently in work mode till near end of week.

I have just 1 specific question - there is 2 parts in the web interface 1 for secure port and the other for non secure - did you also disable them?

Nibbles

dommy · 30-07-2008, 05:04 AM

Hello Nibbles,

Originally Posted by nibbles

Hello Dommy,

Something tells me from reading this, maybe you were looking at a particular howto in regards to trying to setup the N5200 to run a basic website. (just a hunch) however, I remember coming across something about this and I think you might be able to re-enable it via ssh. I am not about to test it on my own box (since I don't need httpd daemon working for this purpose)

I remember reading some notes about this part and will see if there's a way to re-enable it from command level. It might take me a few days since I'm currently in work mode till near end of week.

I have just 1 specific question - there is 2 parts in the web interface 1 for secure port and the other for non secure - did you also disable them?

Nibbles

Thank you for your support, your post as pointed me to the correct way.......

Just tried to connect via the https and it work! Now I have reenabled also the http and all come back.
Thanks to you and all community for support
Cheers
Dommy

nibbles · 31-07-2008, 05:28 PM

WoW! That's good to hear.... Something you might want to keep in mind for next time. In addition the httpd can be pointed to port 80 in which you can do when you setup your webserver module if you like.

Cheers,
Nibbles

Originally Posted by dommy

Hello Nibbles,
Thank you for your support, your post as pointed me to the correct way.......
Just tried to connect via the https and it work! Now I have reenabled also the http and all come back.
Thanks to you and all community for support
Cheers
Dommy

dommy · 31-07-2008, 05:33 PM

Yes,

Originally Posted by nibbles

WoW! That's good to hear.... Something you might want to keep in mind for next time. In addition the httpd can be pointed to port 80 in which you can do when you setup your webserver module if you like.

Cheers,
Nibbles

you are right
Cheers
Dommy

pit234a · 02-08-2008, 10:48 AM

I just followed what you found as source for your problem: you had disabled one port, that is the standard http port.
You would have been able to see this immediately with nmap. Nmap is a simple but effective port scanner and available for almost every platform, at least available for M$ windows too.

pit@syo ~:-> nmap 192.168.0.100

Starting Nmap 4.62 ( http://nmap.org ) at 2008-08-02 11:41 CEST
Interesting ports on 192.168.0.100:
Not shown: 1703 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
80/tcp open http
111/tcp open rpcbind
139/tcp open netbios-ssn
443/tcp open https
445/tcp open microsoft-ds
548/tcp open afp
631/tcp open ipp
905/tcp open unknown
2000/tcp open callbook
2049/tcp open nfs

Nmap done: 1 IP address (1 host up) scanned in 0.184 seconds
pit@syo ~:-> nmap 192.168.0.100

Starting Nmap 4.62 ( http://nmap.org ) at 2008-08-02 11:45 CEST
Interesting ports on 192.168.0.100:
Not shown: 1706 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
111/tcp open rpcbind
443/tcp open https
548/tcp open afp
631/tcp open ipp
891/tcp open unknown
2000/tcp open callbook
2049/tcp open nfs

Nmap done: 1 IP address (1 host up) scanned in 0.132 seconds

dommy · 02-08-2008, 01:31 PM

Originally Posted by pit234a

I just followed what you found as source for your problem: you had disabled one port, that is the standard http port.
You would have been able to see this immediately with nmap. Nmap is a simple but effective port scanner and available for almost every platform, at least available for M$ windows too.

I have installed nmap after your last message and I agree with you that is a nice piece of software.

Cheers
Dommy

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)