@travisdh1 said in Linode host not allowing 80/443:

@wls-itguy said in Linode host not allowing 80/443:

All good. I dove way too deep on this one :crazy_face:

Turns out when I upgraded Moodle I forgot to put a log directory back in place and it was failing on the Apache restart.

I was just gonna ask if you're sure the service that's supposed to respond on those ports was running. That's the first thing I check anymore. Glad you were able to get it sorted.

For some reason I just went deep end because of Linode being involved. Oh well, lesson learned...I hope.

All good. I dove way too deep on this one :crazy_face:

Turns out when I upgraded Moodle I forgot to put a log directory back in place and it was failing on the Apache restart.

I went through the logs a bit and found that this:

[FAILED] Failed to start Load Kernel Modules.

I'm sure this isn't good:

● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2018-07-03 11:09:01 CDT; 35min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 1990 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 1990 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Netstat output:

root@wls-online:~# netstat -plunt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      3480/mysqld         
tcp        0      0 0.0.0.0:110             0.0.0.0:*               LISTEN      3342/dovecot        
tcp        0      0 0.0.0.0:143             0.0.0.0:*               LISTEN      3342/dovecot        
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      2241/rpcbind        
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      3340/sshd           
tcp6       0      0 :::110                  :::*                    LISTEN      3342/dovecot        
tcp6       0      0 :::143                  :::*                    LISTEN      3342/dovecot        
tcp6       0      0 :::111                  :::*                    LISTEN      2241/rpcbind        
tcp6       0      0 :::22                   :::*                    LISTEN      3340/sshd           
udp        0      0 0.0.0.0:111             0.0.0.0:*                           2241/rpcbind        
udp    24576      0 45.79.157.52:123        0.0.0.0:*                           3922/ntpd           
udp        0      0 127.0.0.1:123           0.0.0.0:*                           3922/ntpd           
udp        0      0 0.0.0.0:123             0.0.0.0:*                           3922/ntpd           
udp        0      0 0.0.0.0:721             0.0.0.0:*                           2241/rpcbind        
udp6       0      0 :::111                  :::*                                2241/rpcbind        
udp6       0      0 fe80::f03c:91ff:fe2:123 :::*                                3922/ntpd           
udp6   48384      0 2600:3c03::f03c:91f:123 :::*                                3922/ntpd           
udp6       0      0 ::1:123                 :::*                                3922/ntpd           
udp6       0      0 :::123                  :::*                                3922/ntpd           
udp6       0      0 :::721                  :::*                                2241/rpcbind

Here is the -S output

root@wls-online:~# iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-N f2b-sshd
-A INPUT -p tcp -m multiport --dports 22 -j f2b-sshd
-A f2b-sshd -s 23.102.255.235/32 -j REJECT --reject-with icmp-port-unreachable
-A f2b-sshd -s 58.137.172.213/32 -j REJECT --reject-with icmp-port-unreachable
-A f2b-sshd -j RETURN

This is all greek to me

root@wls-online:~# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
f2b-sshd   tcp  --  anywhere             anywhere             multiport dports ssh

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Chain f2b-sshd (1 references)
target     prot opt source               destination         
REJECT     all  --  58.137.172.213       anywhere             reject-with icmp-port-unreachable
REJECT     all  --  23.102.255.235       anywhere             reject-with icmp-port-unreachable
RETURN     all  --  anywhere             anywhere

Today I got an email from Linode saying that the host that my instance resides on was having issues. After they "fixed it" and rebooted I no longer have access via the web. I can SSH into it but that is all. I am by no means a linux guru so I am not sure where the issue lies.

Last I recall I didn't have any firewall on the server. It is running Debian 9.

Any help would be greatly appreciated!!

I've been using WebSSH

@wls-itguy said in Who's going to SW2018:

I'll be the judge.

I'll be the judge.

@jaredbusch said in Who's going to SW2018:

Things like this are what you find downtown.
https://www.airbnb.com/rooms/9261455
3 beds = 3 people unless one of them is @BRRABill

I'll book it. Anyone want to share? I WILL NOT snuggle or spoon with anyone unless you're really really cute!

Can you get a whole house?

Has anyone already booked an AirBNB? I'd share the cost of space if you have or I can book and someone can share the cost with me

The hotel costs are somewhat REDONK...do the kids still use that word?

@eddiejennings said in Who's going to SW2018:

Looking at flights out of Atlanta. Seems much cheaper than flying direct to Rochester

Flights aren't the issue. The hotel cost is another issue altogether!

The agenda has been out for a bit and some of it looks pretty interesting but I'm sitting on the fence of going.

Anyone else here going?

@jaredbusch said in dns issue? pertino:

I do not know anything about that error.

I trialed Pertino with the original AD integration and it broke shit bad. I never went back to trying it because I left Pertino after CradlePoint bought them.

Sounds like this works better now though.

That's why I keep getting emails from Cradlepoint. Sorry, no answer to the problem

@dbeato said in Windows Update 2018-06 issues:

@wls-itguy said in Windows Update 2018-06 issues:

Anyone else having issues off of the 2018-06 update? I have 1 machine so far that applies the update, reboots, gives me the percentage screen, reboots, and then says Undoing changes, reboots 2-3 times and then goes back to Windows.

I've looked in the logs and it doesn't really give me anything.

Nothing yet so far. Maybe bad drive or not compatible applications.

Looks like I am not the only one LINK

Standard install, nothing spectacular, Avast Business Class AV, Zerotier, and Office 365.

Anyone else having issues off of the 2018-06 update? I have 1 machine so far that applies the update, reboots, gives me the percentage screen, reboots, and then says Undoing changes, reboots 2-3 times and then goes back to Windows.

I've looked in the logs and it doesn't really give me anything.

I know you're working on things but I just wanted to report that none of my machines have checked in since at least May26th. I've rebooted, restarted Salt-Minion to no change.

That is all

@aaronstuder said in Spiceworks Platform API Removal:

I thought we didn't talk about other communities?

• No posting content from other IT communities

https://mangolassi.it/topic/60/our-community-guidelines

I didn't see that fight club rule.