netstat -an Not showing listening ports

Hello,

5.4-STABLE FreeBSD 5.4-STABLE #0: Fri Jul 29

This is a firewall/web server. I can access it with a web browser and I can ssh to it, but netstat -an doesn't show any listening ports.
Any suggestings on how to show what ports are listening?

It does show the listening processes and ports. You just don't have any


This is syslogd listening for connections on all addresses, port 514. But it's UDP, so "listening for a connection" is technically wrong and it doesn't say so.

HTH,
M.

This is active webserver, but it's not listening on port 80?
I'm also running sshd, (and can connect) but no mention of port 22

Are you logged in as root? Maybe you're jail(8)'d.
Is this your own server or rented from an ISP?

M.

Yes it's my server and I'm logged in as root. Although I should have set up a Jail, I didn't.

From another board I was told it might be an error when compiling the new kernel. Somthing about "includes".
I was hoping there was an easier fix I can't afford to take the server down for any extended period of time.

Hmm. Maybe after updating, you rebuilt the kernel but not the userland? ("make buildkernel / installkernel" but not "make buildworld / installworld")

M.

So you think there is no way around it, I'm going to have to build and re-install the kernel?

I don't know. But I've had similar problems before. "ps" didn't work when I used a newer kernel in an older world. This was because they changed some internal structures then.

I'd say try it. You don't have to drop to single user mode for compiling kernel and world. You can do this with all services running, but you'll seriously degrade performance.

After compiling switch to single user mode for installing kernel & world, and run mergemaster. This shouldn't make more than a few minutes of downtime unless something goes wrong (hint: backup ).

M.

Wait a second. You don't need to rebuild userland unless you've built a custom kernel first. So, let's start from the beginning here:

* Are you currently running a custom built kernel or not.
* If yes, you will very likely need to rebuild userland tools as well. This is actually part of the procedure, but a surprising amount of people forget to do it. The symptom of this is that the system will boot and run, but certain commands (e.g.) ps, that refer to certain kernel structures suddenly quit working. These userland tools need to be rebuilt to sync with the new kernel.
* If you didn't build a custom kernel, you don't need to rebuild userland tools either. Problem is elsewhere.

Thanks guys for all the advice.

I also posted this on another board and they are pretty much saying the samething.

After going though my notes (I force myself to write each step down... ya ya I know "psycho" ), I notice I never did make buildworld. I can't afford to make any changes now, but when I do; and confirm that was the problem I'll let you know.

Thanks again for all your suggestions.