Back to Home / #linode / 2019 / 02 / Prev Day | Next Day
#linode IRC Logs for 2019-02-12

---Logopened Tue Feb 12 00:00:01 2019
00:32-!-Rudy [rudy@2600:3c00::f03c:91ff:fedf:91b4] has quit [Quit: ZNC 1.7.1 -]
00:33-!-Rudy [] has joined #linode
00:33-!-Rudy is "Rudy Valencia" on #virt #pandorah #linode #Corsair #moocows
02:04-!-redentor [] has quit [Remote host closed the connection]
02:16-!-Edgeman [] has joined #linode
02:16-!-Edgeman is "Edgeman" on #linode
02:18-!-Sachin [~oftc-webi@] has joined #linode
02:18-!-Sachin is "OFTC WebIRC Client" on #linode
02:24-!-Sachin [~oftc-webi@] has left #linode []
04:06<linbot>New news from community: I'm having trouble connecting to my server and the ssh service is running. <>
04:27-!-thiras [~thiras@] has joined #linode
04:27-!-thiras is "Ant" on #tami #linode #debian
06:14-!-thiras [~thiras@] has quit [Ping timeout: 480 seconds]
08:14<jfbourdeau>Good morning gentlemans. 1) has anyone ever tried to install pfsense or opensense firewall on a Linode ? 2) Can we linked several public IP to one linode ( in my example, a firewall linode)
08:32-!-HKJournalist [] has joined #linode
08:32-!-HKJournalist is "OFTC WebIRC Client" on #linode
08:33-!-HKJournalist [] has left #linode []
08:53-!-anomie [] has joined #linode
08:53-!-anomie is "Anomie" on #linode
09:27-!-thiras [~thiras@] has joined #linode
09:27-!-thiras is "Ant" on #debian #linode #tami
09:45-!-shentino_ [~shentino@] has quit [Remote host closed the connection]
09:48-!-shentino [~shentino@] has joined #linode
09:48-!-shentino is "realname" on #linode #tux3
09:58-!-asilverman [~aaron@2600:3c03::f03c:91ff:fef0:6cce] has joined #linode
09:58-!-asilverman is "aaron" on #linode
10:01-!-asilverman [~aaron@2600:3c03::f03c:91ff:fef0:6cce] has quit []
10:05-!-redentor [] has joined #linode
10:05-!-redentor is "realname" on #debian-mx #debian-es #debian #linode
10:15-!-redentor [] has quit [Remote host closed the connection]
11:15-!-VladGh [] has quit [Quit: Lost terminal]
11:16-!-VladGh [] has joined #linode
11:16-!-VladGh is "Vlad" on #linode
11:37<linbot>New news from community: Backup service for the new Cloud Manager <>
11:44-!-Peng [] has quit [Quit: Peng timeout]
11:44-!-Peng [] has joined #linode
11:44-!-Peng is "Matt Nordhoff" on #launches #privacytech #tor-project #Corsair #tor-dev #linode-beta #english #help #moocows #python #opendns #oftc #linode
11:44-!-thiras [~thiras@] has quit [Ping timeout: 480 seconds]
11:44-!-thiras [~thiras@] has joined #linode
11:44-!-thiras is "Ant" on #debian #linode #tami
11:58-!-atrus_ is now known as atrus
11:59-!-thiras [~thiras@] has quit [Ping timeout: 480 seconds]
12:12-!-thiras [~thiras@] has joined #linode
12:12-!-thiras is "Ant" on #debian #linode #tami
12:22-!-thiras [~thiras@] has quit [Ping timeout: 480 seconds]
12:22-!-thiras [~thiras@] has joined #linode
12:22-!-thiras is "Ant" on #debian #linode #tami
12:32-!-thiras [~thiras@] has quit [Ping timeout: 480 seconds]
12:42-!-thiras [~thiras@] has joined #linode
12:42-!-thiras is "Ant" on #debian #linode #tami
12:53-!-thiras [~thiras@] has quit [Ping timeout: 480 seconds]
13:06-!-thiras [~thiras@] has joined #linode
13:06-!-thiras is "Ant" on #debian #linode #tami
13:20-!-marshmn [~matt@] has joined #linode
13:20-!-marshmn is "Matt Marsh" on #linode
13:23-!-blaboon [] has joined #linode
13:23-!-blaboon is "Bradley LaBoon" on #linode
13:23-!-mode/#linode [+o blaboon] by ChanServ
13:24<Peng_>Minor routing issue in Dallas?
13:27<dwfreed>Peng_: mtr? :P
13:27<Peng_>!mtr-dallas -nzc 8
13:27<Peng_>it's DO AMS or something
13:27<linbot>Peng_: ('The read operation timed out',)
13:27<Peng_>!mtr-dallas -nzc 8
13:27<linbot>Peng_: [mtr-dallas] 12. AS6453 2a01:3e0:ff40:200::22 0.0% 8 107.5 113.4 107.2 152.8 15.9 -- 13. AS??? ??? 0.0% 0 0.0 0.0 0.0 0.0 0.0 -- see for full mtr
13:27<dwfreed>you really should fix that :P
13:28<Peng_>linbot should have a higher timeout :D
13:29<linbot>Error: should is not a valid command.
13:30<Peng>Whoops, Tilaa, not DigitalOcean
13:31<dwfreed>it was Tata -> Tilaa
13:32<dwfreed>MTR is working now
13:32<Peng_>!mtr-dallas -nzc 8 fin
13:32<linbot>Peng_: ('The read operation timed out',)
13:33<dwfreed>works here
13:33<dwfreed>!mtr-dallas -nzc 8
13:34<dwfreed>that's my test point
13:34<linbot>dwfreed: ('The read operation timed out',)
13:34<dwfreed>!mtr-dallas -nzc 8
13:34<linbot>dwfreed: [mtr-dallas] HOST: clover Loss% Snt Last Avg Best Wrst StDev -- 1. AS63949 2600:3c00::f03c:91ff:fe04:779 0.0% 8 0.6 0.6 0.3 1.5 0.0 -- see for full mtr
13:35<dwfreed>both the 01 and the 02 address work
13:35<dwfreed>mtr by name kept getting the 02 address
13:37<Peng_>Still not better for me. With some IPs. Other IPs work!
13:38<Peng_>ntpd, in one direction, hasn't succeeded for 80 minutes. Nice.
15:24-!-anomie [] has quit [Ping timeout: 480 seconds]
15:32-!-anomie [] has joined #linode
15:32-!-anomie is "Anomie" on #linode
15:44-!-redentor [] has joined #linode
15:44-!-redentor is "realname" on #debian-mx #debian-es #debian #linode
16:52-!-marshmn [~matt@] has quit [Ping timeout: 480 seconds]
17:00-!-anomie [] has quit [Remote host closed the connection]
17:10<linbot>New news from community: What are Your Default DNS Servers <>
17:57-!-jfbourdeau [~youpet3@] has quit [Remote host closed the connection]
18:06-!-chattadude [~david@] has joined #linode
18:06-!-chattadude is "purple" on #linode
18:11<chattadude>I think one of our servers is undergoing a DDoS attack. At first, I thought it might be underlying hardware issues, as the server took absolutely forever to come up after a reboot, and I kept seeing lots of timeouts, such as:
18:11<chattadude>kernel:watchdog: BUG: soft lockup - CPU#1 stuck for 21s! [ksoftirqd/1:22]
18:11<chattadude>But we stopped Apache, and while it took load quite a bit of time to fall, fall it did.... and it didn't go up again until we started Apache again
18:13<chattadude>If its DDoS, it's a sly attack. This is a shared server, and it doesn't appear to be an issue with any single particular website
18:13<chattadude>I'm currently running a tcpdump on port 443, but if anyone has any suggestions, or if there's anything the Linode staff might be able to do upstream to help detect what's going on, I'd appreciate it
18:15<@mcintosh>do you have a ticket open?
18:15<chattadude>I do, but that was when I first suspected underlying hardware issue
18:15<chattadude>As of now, I'm not so sure it is hardware related
18:20<chattadude>Ok, possibly getting somewhere. I'm seeing TONS of ack packets in Wireshark.
18:28<chattadude>I still haven't heard back from the support ticket I opened up about 30 minutes ago.
18:28<chattadude>I just opened up a new, separate ticket for the possible DDoS and help around that
18:37-!-blaboon [] has quit [Remote host closed the connection]
18:43-!-blaboon [] has joined #linode
18:43-!-blaboon is "Bradley LaBoon" on #linode
18:43-!-mode/#linode [+o blaboon] by ChanServ
19:13<chattadude>still no answer to either of my tickets....
19:14<chattadude>We're beginning to migrate websites over to a stable server at a different provider in the hopes we can more quickly narrow down and stabilize the issue (whatever that issue is)
19:18<chattadude>At this point, doesn't seem to be anyone present with Linode here on this channel. Getting pretty frustrated at lack of response.
19:38<Abi12>why not just call support?
19:38<Abi12>I always call when it's urgent. Also -
19:38<linbot>Users with ops are employees of Linode, and know what they're talking about. The rest of us are the ever-so-helpful(?) community. Official Linode contact information:
19:42<Abi12>Also, what's leading you to believe it's a DOS attack or a underlying hardware issue? Are you sure your configuration is that airtight?
19:46<chattadude>wait, there's a phone number?!?
19:46<chattadude>unbelievable. Yes there is.
19:47<Abi12>Yes. It's on their homepage at the bottom under 'Contact Us'.
19:47<chattadude>anyway, I did just get a response. They've confirmed they are seeing very high load on the host machine, and are working on migrating our VM to a different host
20:00-!-copart [] has joined #linode
20:00-!-copart is "copart" on #linode
20:03-!-Unit193 [] has quit [Ping timeout: 600 seconds]
20:15-!-Unit193 [] has joined #linode
20:15-!-Unit193 is "Unit 193" on #debian-berlin @#pastly-log2 #osm-us #debian-blends #kgb-devel #debian-next #linode #freenode #ohiolinux #devscripts #oftc-status #oftc-staff #debian-ayatana #mapreri #debian-edu #debian-apt #bitrig #oftc #debian-ruby #debian-live #neurodebian #CipherShed #packaging #debian-devel-changes #debian-games #debian-multimedia #lxde
20:52-!-blaboon [] has quit [Remote host closed the connection]
21:40-!-Leo_ [] has joined #linode
21:40-!-Leo_ is "OFTC WebIRC Client" on #linode
21:40<Leo_>Is that legal for put something like adult content in your server ?
22:11-!-redentor [] has quit [Remote host closed the connection]
22:23<Cromulent>hmm since when did Linode introduce dedicated CPU instances? I obviously haven't been paying attention recently
22:23<Cromulent>oh Feb 5th
22:23<Cromulent>that is pretty cool though I have to say
22:30-!-Leo_ [] has quit [Quit: Page closed]
22:40-!-tech62939 [] has joined #linode
22:40-!-tech62939 is "OFTC WebIRC Client" on #linode
22:57-!-jtothek [~oftc-webi@] has joined #linode
22:57-!-jtothek is "OFTC WebIRC Client" on #linode
22:58-!-jtothek [~oftc-webi@] has quit []
23:26<@mcintosh>Cromulent: thanks :3
23:39<chattadude>FWIW, I was right -- it was a problem with the underlying physical host. Finally back up and running, but that was after I manually restored two websites onto another server from backups. I'm glad I didn't have to restore any others though. I could have been up half the night.
23:39-!-chattadude [~david@] has quit [Quit: Leaving.]
23:59-!-KindOne [] has quit [Read error: No route to host]
---Logclosed Wed Feb 13 00:00:02 2019