eve-ng web console suddenly unreachable

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
heidebock
Posts: 8
Joined: Tue Oct 30, 2018 1:17 pm

eve-ng web console suddenly unreachable

Post by heidebock » Sat May 09, 2020 1:56 pm

Hello,
for some reason eve-ng has stopped listening on port 443/80/etc. I can still access the server via SSH & all simulated devices are still running just fine in the lab (I can reach all of them, etc.). It's a rather complicated lab so I'd rather not reload. Is there a way to simply reset the web-server, etc?

I've checked all intermediate firewalls and the required ports are open, but eve-ng doesn't seem to be listening on the appropriate ports anymore.

Any suggestions on how to recover the CLI w/out a reload?

thanks!
Erik

(eve-ng background server info at the bottom)

Code: Select all

** eve-ng server **

root@eve-lab:~# netstat -tlpn | egrep "^tcp\s+"
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      6870/sshd
tcp        0      0 127.0.0.1:4822          0.0.0.0:*               LISTEN      6873/guacd
tcp        0      0 0.0.0.0:6653            0.0.0.0:*               LISTEN      6943/ovs-testcontro
tcp        0      0 0.0.0.0:2049            0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:32770           0.0.0.0:*               LISTEN      25091/qemu-system-x
tcp        0      0 0.0.0.0:32835           0.0.0.0:*               LISTEN      46871/dynamips
tcp        0      0 0.0.0.0:37193           0.0.0.0:*               LISTEN      6876/rpc.mountd
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      6853/mysqld
tcp        0      0 0.0.0.0:32843           0.0.0.0:*               LISTEN      59035/qemu-system-x
tcp        0      0 0.0.0.0:43851           0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:39179           0.0.0.0:*               LISTEN      6876/rpc.mountd
tcp        0      0 0.0.0.0:55855           0.0.0.0:*               LISTEN      6876/rpc.mountd
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      6859/rpcbind

** FROM REMOTE **

MacBook-Pro:~ home$ sudo nmap -sT 10.14.208.10
Starting Nmap 7.80 ( https://nmap.org ) at 2020-05-09 15:38 CEST
Nmap scan report for 10.14.208.10
Host is up (0.17s latency).
Not shown: 979 closed ports
PORT      STATE    SERVICE
22/tcp    open     ssh
111/tcp   open     rpcbind
2049/tcp  open     nfs
3389/tcp  filtered ms-wbt-server
32769/tcp open     filenet-rpc
32770/tcp open     sometimes-rpc3
32771/tcp open     sometimes-rpc5
32772/tcp open     sometimes-rpc7
32773/tcp open     sometimes-rpc9
32774/tcp open     sometimes-rpc11
32775/tcp open     sometimes-rpc13
32776/tcp open     sometimes-rpc15
32777/tcp open     sometimes-rpc17
32778/tcp open     sometimes-rpc19
32779/tcp open     sometimes-rpc21
32780/tcp open     sometimes-rpc23
32781/tcp open     unknown
32782/tcp open     unknown
32783/tcp open     unknown
32784/tcp open     unknown
32785/tcp open     unknown

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

Eriks-MacBook-Pro:~ home$ sudo hping3 -S 10.14.208.10 -p 443
HPING 10.14.208.10 (en8 10.14.208.10): S set, 40 headers + 0 data bytes
len=46 ip=10.14.208.10 ttl=49 DF id=10578 sport=443 flags=RA seq=0 win=0 rtt=169.6 ms
len=46 ip=10.14.208.10 ttl=49 DF id=10755 sport=443 flags=RA seq=1 win=0 rtt=173.2 ms

(being rejected by host)

** intermediate FW **

ZBF-ROUTER#sho policy-map type inspect zone-pair A-TO-B_ZBF sessions | i 10.14.208.10
         Session ID 0xC7C0ED08 (10.136.174.142:62173)=>(10.14.208.10:22) ssh SIS_OPEN
         Session ID 0xD0C6EB4C (10.136.174.142:1654)=>(10.14.208.10:443) https SIS_CLOSED


ZBF-ROUTERsho policy-map type inspect zone-pair C-TO-D_ZBF sessions | i 10.14.208.10
         Session ID 0xC7C0ED0E (10.12.17.62:62173)=>(10.14.208.10:22) ssh SIS_OPEN
         Session ID 0xD0CF8D38 (10.12.17.62:50592)=>(10.14.208.10:443) https SIS_CLOSED
         

* server-info

Code: Select all

-bare-metal

root@eve-lab:~# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                72
On-line CPU(s) list:   0-71
Thread(s) per core:    2
Core(s) per socket:    18
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 79
Model name:            Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.30GHz

root@eve-lab:~# dpkg -l eve-ng
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                    Version          Architecture     Description
+++-=======================-================-================-====================================================
ii  eve-ng                  2.0.3-92         amd64            A new generation software for networking labs.



root@eve-lab:~# df -h
Filesystem                     Size  Used Avail Use% Mounted on
udev                           252G     0  252G   0% /dev
tmpfs                           51G  309M   51G   1% /run
/dev/mapper/eve--lab--vg-root  376G   80G  277G  23% /
tmpfs                          252G     0  252G   0% /dev/shm
tmpfs                          5.0M     0  5.0M   0% /run/lock
tmpfs                          252G     0  252G   0% /sys/fs/cgroup
/dev/sda1                      472M   83M  365M  19% /boot

Uldis (UD)
Posts: 5084
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: eve-ng web console suddenly unreachable

Post by Uldis (UD) » Sat May 09, 2020 1:59 pm

check if your apache service is working..
restart maybe

to start apache web server:

systemctl start apache2

to check status apache2:

systemctl status apache2

heidebock
Posts: 8
Joined: Tue Oct 30, 2018 1:17 pm

Re: eve-ng web console suddenly unreachable

Post by heidebock » Mon May 11, 2020 9:59 am

thanks, restart of the apache2 service worked! Sorry for such a basic question but I wasn't sure which web engine eve-ng was using.

Post Reply