Troubleshooting · Lesson 14 of 26 · 8 minutes

Incident unknown listener

Map a listener to process and firewall evidence.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Show listeners
Run ss -tulpn.
Hint & worked example
Inspect simulated listening sockets and connection information.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ss -tulpn
```
Remember: A listening socket is not proof of correct application responses or external reachability.
2
Show socket owners
Run lsof -i.
Hint & worked example
Inspect a synthetic association between processes and open files or sockets.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
lsof -i
```
Remember: Combine process and socket evidence rather than assuming a service from its port number.
3
Show firewall
Run ufw status verbose.
Hint & worked example
Inspect or adjust the training firewall rule list. No real firewall changes occur.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
ufw status verbose
```
Remember: Firewall rules should be scoped and reviewed; simulator access is not a production change approval.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

ss: Inspect simulated listening sockets and connection information.
A listening socket is not proof of correct application responses or external reachability.
lsof: Inspect a synthetic association between processes and open files or sockets.
Combine process and socket evidence rather than assuming a service from its port number.
ufw: Inspect or adjust the training firewall rule list. No real firewall changes occur.
Firewall rules should be scoped and reviewed; simulator access is not a production change approval.

Worked example and expected result

$ ss -tulpn

Netid State  Local Address:Port  Process
udp   UNCONN 0.0.0.0:68          lab-dhcp
tcp   LISTEN 0.0.0.0:22          sshd
tcp   LISTEN 0.0.0.0:80          nginx
tcp   LISTEN 0.0.0.0:443         nginx

Exit status: 0. The command completed successfully in the training fixture.

$ lsof -i

COMMAND PID USER   FD  TYPE NAME
nginx    42 www    6u  IPv4 *:80 (LISTEN)
nginx    42 www    7u  IPv4 *:443 (LISTEN)
sshd     77 root   3u  IPv4 *:22 (LISTEN)

Exit status: 0. The command completed successfully in the training fixture.

$ ufw status verbose

Status: active
Logging: on (simulated)
Default: deny incoming, allow outgoing
- allow 22/tcp
- allow 80/tcp
- allow 443/tcp
- deny 23/tcp

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Incident unknown listener”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.Combine process and socket evidence rather than assuming a service from its port number.

Apply it elsewhere

Before adapting the lsof workflow from “Incident unknown listener” to another server, what should you do?Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Incident permission denied Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual