kihei/i-0fd2941b6817bc7a9
by SadServersMore by SadServers
fsck from util-linux 2.36.1 e2fsck 1.46.2 (28-Feb-2021) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/nvme2n1p1 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> admin@i-0eacfe699faffbd49:~$
kihei/i-0eacfe699faffbd49 05:33
by SadServersdrwxr-xr-x 2 admin root 4.0K Sep 24 23:20 agent -rwxrwx--- 1 root root 360 Sep 24 23:20 webserver.py admin@i-0a40943c8c217e6da:~$ vim webserver.py admin@i-0a40943c8c217e6da:~$ sudo su We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility. [sudo] password for admin: Sorry, try again. [sudo] password for admin:
paris/i-0a40943c8c217e6da 00:30
by SadServersexample: knock myserver.example.com 123:tcp 456:udp 789:tcp admin@i-080ac908debd2d3d7:~$ knock -v 127.0.0.1 80:tcp 1 hitting tcp 127.0.0.1:80 hitting tcp 127.0.0.1:1 admin@i-080ac908debd2d3d7:~$ knock -v 127.0.0.1 80:tcp hitting tcp 127.0.0.1:80 admin@i-080ac908debd2d3d7:~$ curl -D - -v localhost * Trying 127.0.0.1:80... * connect to 127.0.0.1 port 80 failed: Connection refused * Failed to connect to localhost port 80: Connection refused * Closing connection 0 curl: (7) Failed to connect to localhost port 80: Connection refused admin@i-080ac908debd2d3d7:~$ nc -vv 12