How to reinstall web server (port 9999)

[PhunkyBob]

Hi !

I tried to install "lighttpd" with the CSI. After 2 hours, the install was still running. I closed the CSI.
Since this time, my PCH has some problems.

I tried to install "lighttpd" in command line, but it seems to fail ("Checking Application Initializer profile: Valid", then nothing...).

When I reboot the PCH, all my PCH services are "starting", but don"t start.
I renamed the "/share/Apps/AppInit" and done another reboot.

Now, I can't see any Web Application (transmission, NZBget). When I try to reinstall with the CSI, it stays with a "processing" status.


I would like to get my original web server back.

How can I do that ?


Thank you for your help...

[shinma]

*bump*

Having the same problem. Anything on 9999 won't come up, even though 8883 apps still work fine and can be accessed from a browser.

[Ger Teunis]

Please uninstall lighttpd and restart the NMT.
Then install lighttpd again and try again.

If that doesn't work try a complete reinstall of the NMT apps
http://www.networkedmediatank.com/wiki/i...g_NMT_Apps

Hope that helps.

[Paardekam.nl]

(12-05-2009 02:44 PM)Ger Teunis Wrote:  Please uninstall lighttpd and restart the NMT.
Then install lighttpd again and try again.

If that doesn't work try a complete reinstall of the NMT apps
http://www.networkedmediatank.com/wiki/i...g_NMT_Apps

Hope that helps.

Thanks Ger! Re-installing lighttpd did the trick for me!

[tiefling]

(12-05-2009 02:44 PM)Ger Teunis Wrote:  Please uninstall lighttpd and restart the NMT.
Then install lighttpd again and try again.

If that doesn't work try a complete reinstall of the NMT apps
http://www.networkedmediatank.com/wiki/i...g_NMT_Apps

Hope that helps.

As of this afternoon, any web apps on Port 9999 that I try to access (NZBGet Web, CSI Gaya etc.) all fail with a 404 error.

Lighttpd based apps like Oversight and Feedtime, runnning on Port 8883 seem unaffected.

Any ideas where I can start looking at this problem? The only recent addition i've made to my NMT is the LundMan shell.

Tried uninstalling lighttpd - Now my 999 port items give me...

Forbidden

You don't have permission to access /CSI Gaya_web/ on this server.
Apache/1.3.33 Server at 192.168.1.150 Port 9999

Re-installed lighttpd and now I'm getting '404' errors again.

---

(03-27-2010 01:24 AM)tiefling Wrote:  As of this afternoon, any web apps on Port 9999 that I try to access (NZBGet Web, CSI Gaya etc.) all fail with a 404 error.

Lighttpd based apps like Oversight and Feedtime, runnning on Port 8883 seem unaffected.

Any ideas where I can start looking at this problem? The only recent addition i've made to my NMT is the LundMan shell.

Tried uninstalling lighttpd - Now my 999 port items give me...

Forbidden

You don't have permission to access /CSI Gaya_web/ on this server.
Apache/1.3.33 Server at 192.168.1.150 Port 9999

Re-installed lighttpd and now I'm getting '404' errors again.

I managed to get everything up and working again by reinstalling all my CSI apps - v odd!

[mikesleves]

First, You have to uninstall Web server plug-ins for Application Server without uninstalling the supported Web server or the application server. Then You are able to re-installs the web server. Then, If you used the IBM Key Management wizard to create SSL key files in the Web server Plug-ins home directory, back up the files to a directory outside of the Web server Plugins directory.

[tiefling]

(03-29-2010 08:51 AM)mikesleves Wrote:  First, You have to uninstall Web server plug-ins for Application Server without uninstalling the supported Web server or the application server. Then You are able to re-installs the web server. Then, If you used the IBM Key Management wizard to create SSL key files in the Web server Plug-ins home directory, back up the files to a directory outside of the Web server Plugins directory.

I think you've got the wrong end of the stick - This is with the C-200 lighttpd web server. When you remove lighttpd then it defaults back to the built in Apache instance.

[schizoduckie]

(03-29-2010 09:42 AM)tiefling Wrote:  I think you've got the wrong end of the stick - This is with the C-200 lighttpd web server. When you remove lighttpd then it defaults back to the built in Apache instance.

I think something must be wrong with the autostart script. It does work with me right after i install LightHTTPD with CSI, until after reboot it.

I've only set my first steps into hacking this thing yesterday, but i'll take a look later tonight, hope that i can get a shell working and check some logs.

In the meantime, is there some kind of log what the CSI does when it's installing something? The key to the solution might be in there. (since it is able to start it after the installation)

[Ger Teunis]

All can be found in the install scrip of lighttpd, it is a know issue that stopping the current httpd server fails for some users and thus resulting in that port 9999 will not get released for the lighttpd server.
It should be solved in the install script of lighttpd package.

[schizoduckie]

(08-03-2010 06:24 PM)Ger Teunis Wrote:  All can be found in the install scrip of lighttpd, it is a know issue that stopping the current httpd server fails for some users and thus resulting in that port 9999 will not get released for the lighttpd server.
It should be solved in the install script of lighttpd package.

Known issue, any specific directions? to bug and fix? I'd like this to work for me tonight

Shouldn't this then be solved if you do an install, reboot, get no response on 9999, and then install again? (because that doesn't work either)