Web Interface not starting on Linux

Discussion in 'Other ESET Home Products' started by sss84, Jul 26, 2011.

Thread Status:
Not open for further replies.
  1. sss84

    sss84 Registered Member

    Joined:
    Jul 26, 2011
    Posts:
    3
    Hello,

    I've got a problem with getting the Web Interface for the ESET File Security package I've installed running.

    I'm running Fedora 11, and have followed the instructions HERE. But at step 8, after restarting the eset_daemon service the wwwi module doesn't start up.

    Here's the output of the command to check service:
    Code:
    [root@fileserver esets]# ps -e | grep esets
    25435 ?        00:00:00 esets_daemon
    25436 ?        00:00:05 esets_daemon
    
    No wwwi process

    Here's the wwwi portion of the eset.cfg file:
    Code:
    [wwwi]
    # Settings for ESETS Web Interface configuration module
    
    # agent_enabled = yes/no
    # Enables operation of the esets_wwwi.
    agent_enabled = yes
    
    # listen_addr = "address"
    # Address (IP or name) where esets_wwwi listens for HTTPS client connections.
    # If set to 0.0.0.0 then esets_wwwi listens on all available network interfaces.
    listen_addr = "0.0.0.0"
    
    # listen_port = port
    # TCP port where esets_wwwi listens for HTTPS client connections.
    # You may have to open this port in your firewall.
    listen_port = 9999
    
    # username and password needed for accessing the interface (required)
    username = "test"
    password = "test"
    
    Any ideas on why the wwwi process isn't starting?

    Thanks
     
  2. MattJN

    MattJN Former ESET Support Rep

    Joined:
    Feb 19, 2010
    Posts:
    149
    Hello,

    I'm wondering if perhaps another service (non-eset related) is listening on the port. Try running this from the terminal and see if that lends any clues:

    netstat -an | grep LISTEN | grep 9999

    Thanks,

    Matt
     
  3. sss84

    sss84 Registered Member

    Joined:
    Jul 26, 2011
    Posts:
    3
    Thanks for reply MattJN.

    I ran that command but it didn't return any results. :(

    Is there a way to start the process manually (ie not via the eset deamon)?
    Any logs I should be looking in? (sorry I've only intermediate linux knowledge)
     
    Last edited: Jul 28, 2011
  4. sss84

    sss84 Registered Member

    Joined:
    Jul 26, 2011
    Posts:
    3
    Any further ideas on what might be wrong or how to investigate this issue?
     
Thread Status:
Not open for further replies.