List of good troubleshooting commands?

[nharel]

Sorry to ask a stupid question, but how/where do you run these commands?

[hlarsen]

you can run them from the terminal or through SSH.

[coltect]

iftop -pPnNB -i eth0
or eth1 etc
You can use filters like this
iftop -pPnNB -i eth1 -f 'port 25' to watch email coming in before it gets processed.
or -f 'host 10.20.30.40' or -f 'host hostname.to.watch'

Very similar to jnettop, but I like iftop, and it works on many firewall/utm distros.

[sky-knight]

Yeah both tools are very different. I like jnettop because I can switch interfaces without restarting the tool. But iftop's interface is easier to read certain things and see the relative consumption of individual network sessions.

Both are very powerful to have around. Neither have I needed since the session viewer was added.

[milen]

Post-installation, using commands to troubleshoot/verify various interface/NIC properties or issues.
These are general Linux troubleshooting commands, so not really 100% on topic, but may help a fellow Untangler.

Q. Need to verify network cards duplex/speed - don't assume that autonegotiation always works.
1. mii-tool -v eth0
mii-tool is a bit old, won't work on Gigabit, but is still useful on older boxes.
2. ethtool eth0

Q. NIC card not visible/not identified by Untangle.
1. Check if it was discovered by the kernel in the kernel boot log
dmesg
2. Check if it's in the list of detected PCI devices
lspci
3. Check if the kernel has loaded the required module for your NIC
lsmod

Q. View the routing table, making sure all your networks are visible/accessible.
netstat -rn

[mobiledev]

Add web user from terminal no longer working?

You can with a terminal root access add a new account.

Code:

ucli passwd -a username password

Then you can login to the webgui with the new user id and password.

Original from Webfool in webfilter sub thread

ucli doesn't accept this command any more. Is there another way to do this?

[jcoffin]

ucli doesn't accept this command any more. Is there another way to do this?

Use the GUI, not the command line.

[mobiledev]

I can't get into the GUI. Changed the password and went on vacation, now it's gone (out of my head). I have the root password from when I initially set the box up.

[jcoffin]

Open a support ticket, they can help you.

[goodDay14]

I'm wondering if there is a consolidated list of helpful UT troubleshooting commands somewhere. I've seen commands to check the database size, check disk space, check to see what applications are installed and/or running, etc. I've also seen and used top and jnettop. I still feel like I really don't know what to look for if I'm having a problem and I'd like to be a little more self-sufficient.

What other commands have you all found helpful?

I'd like to find out more about the ucli commands available. It seems to be useful, but I can't find any documentation on it.

[jcoffin]

I'd like to find out more about the ucli commands available. It seems to be useful, but I can't find any documentation on it.

Commands on the terminal or ssh are not supported are are at your own risk so are not documented.

[talkybro1]

I'd like to find out more about the ucli commands available. It seems to be useful, but I can't find any documentation on it.

[donhwyo]

If you have support click the "?Help" button to the lower right of this page. Using the cli will void your support. Might be available during the trial too?

If you are a home user this is your support. Just ask and someone will probably try to help. Generic trouble shooting is documented all over the internet just search. Even some on these forums.

Good luck

[sky-knight]

Over the years, Untangle has improved such that even I don't need the command line anymore. The only time I'm in there is to use top and other system level tools to get statistics on hardware performance and system health. These things are Debian Linux, and anyone familiar with that family of operating systems can easily handle all that safely on their own. There's no need for more documentation here on that topic.

The ucli command is still there... but again you shouldn't need it. There are some niche circumstances where command line work is required to get things sorted out. But those are more the exception than the rule, and becoming even more exceptional by the day. This thread goes all the way back to 2010, and I shudder to think how much incorrect information must be here.

If you're proficient with Debian Linux, and you want to play under the hood. Knock yourself out, it's open source for a reason. But also, all of that is unsupported for a reason. So if you muck around in there and have strange problems, we're just going to tell you to nuke your box and start over. Because it's the only way to get the install back into a known good configuration.