Help to restore server

Issues related to configuring your network
Post Reply
ZTec
Posts: 2
Joined: 2018/03/30 14:39:37

Help to restore server

Post by ZTec » 2018/03/30 18:48:36

Hello All,
I am still a novice with centos, so please bear with me. I have a personal/test server set up with a LAMP stack, vhosts, wordpress, firewalld, and fail2ban. I experimented with trying to add virtual email functionality as a learning exercise using the linode guide to setup postfix & dovecot, but something went wrong somewhere and now my server won't respond to browser requests or SSH connections. I figure I broke a config somewhere in one of these so I removed postfix & dovecot as well as all the databases and config files & folders that stayed. Restarted sshd, httpd, and mariadb, then I did a hard reboot on the whole server, but still not able to get it to respond. It's also difficult for me to post logs as my server's emergency console does not allow me to copy anything from it. I can, however attach screenshots instead...I have one of the /var/log/secure log, but it's over the size limit, which is weird...maybe because it's a screen full of text, more pixels to translate to grey instead of leaving them black.
Attachments
firewalldscreen.jpg
firewalldscreen.jpg (248.19 KiB) Viewed 763 times
screen1.jpg
screen1.jpg (216.02 KiB) Viewed 764 times

jscarville
Posts: 135
Joined: 2014/06/17 21:50:37

Re: Help to restore server

Post by jscarville » 2018/03/30 20:47:10

A few thing come to mind. First check that you are actually listening on the correct ports.

# ss -natp|grep LISTEN

Next make sure your network has not been munged

# ip addr

# ip route list

If the above are correct and you have a place to scan the system from (or a trustworthy friend) try using nmap to determine what services are actually available.

# nmap -A -T4 ip.add.re.ss

ZTec
Posts: 2
Joined: 2018/03/30 14:39:37

Re: Help to restore server

Post by ZTec » 2018/03/30 22:26:31

jscarville wrote:A few thing come to mind. First check that you are actually listening on the correct ports.

# ss -natp|grep LISTEN

Next make sure your network has not been munged

# ip addr

# ip route list

If the above are correct and you have a place to scan the system from (or a trustworthy friend) try using nmap to determine what services are actually available.

# nmap -A -T4 ip.add.re.ss
Yep! You found my issue! Thank you! Luckily Rackspace has Pitchfork APIs so I was able to run a reset network API call & fix it.

See image attachment for before.

After:

Code: Select all

[ZTec@server-01 ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether bc:76:4e:02:53:12 brd ff:ff:ff:ff:ff:ff
    inet 23.253.92.151/24 brd 23.253.92.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2001:4800:7815:105:be76:4eff:fe02:5312/64 scope global
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether bc:76:4e:02:70:d8 brd ff:ff:ff:ff:ff:ff
    inet 10.208.99.114/19 brd 10.208.127.255 scope global eth1
       valid_lft forever preferred_lft forever
Attachments
ipscreen.jpg
ipscreen.jpg (236.32 KiB) Viewed 744 times

Post Reply