I started the thread at http://ubuntuforums.org/showthread.php?t=855562 but they seem unable to help me. Does anyone here have any ideas on how to solve my problem?

(I can see in GNOME System Monitor that the programs are running, yet the ports they are supposed to open do not work.)

Two things:

Perform a netstat -an to make sure that the ports are open.

Use telnet to make sure that the ports are service HTTP. Do this by trying the command telnet 127.0.0.1 8001 or some variation of that.

These two suggestions will make sure that the services are actually acting on those port requests and if they are indeed serving HTTP.

That put out way to much information. What I needed had scrolled by, past the top of where I can scroll up to. I did netstat -n -l, though, and got:
jaredtbrees@multiboot:~$ netstat -n -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:8001 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8002 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3128 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3389 0.0.0.0:* LISTEN
tcp6 0 0 :::5900 :::* LISTEN
tcp6 0 0 :::53 :::* LISTEN
tcp6 0 0 :::631 :::* LISTEN
udp 0 0 0.0.0.0:53 0.0.0.0:*
udp 0 0 0.0.0.0:3130 0.0.0.0:*
udp 0 0 0.0.0.0:68 0.0.0.0:*
udp 0 0 0.0.0.0:43084 0.0.0.0:*
udp 0 0 0.0.0.0:51796 0.0.0.0:*
udp 0 0 0.0.0.0:56036 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:*
udp 0 0 0.0.0.0:631 0.0.0.0:*
udp6 0 0 :::53 :::*



as for telnet...


jaredtbrees@multiboot:~$ telnet 127.0.0.1 8001
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection timed out

Though the output was timed like:

jaredtbrees@multiboot:~$ telnet 127.0.0.1 8001
Trying 127.0.0.1...Wait five minutes, then:
telnet: Unable to connect to remote host: Connection timed out

I timed it. So, what does all this mean? (According to netstat, they're open; according to telnet, they're not?!?)

Seems like you have a lot on your hands there.

If you claim that there is no firewall, there is a service listening on the ports, but there is not response on the port then I would suspect the service.

Have you tried running the service on a different port(s)?
Have you tried reinstalling the service and making sure that all dependencies are installed and available?

Consult your logs to see if you can find anything on your service.

As for telnet, when you connect try typing a few letters and then pressing enter a few times. This usually returns HTML code from the server if connected.

I don't know for sure about the firewall... How can I tell for sure?

As for typing letters in telnet, that's the problem: I can't connect at all; it times out.

Yes, I have uninstalled and reinstalled and it didn't fix it. Keep in mind it used to work, it just quit one day.

That's understandable about the firewall. I looked at your previous posts on ubuntuforums.org where you said there was no firewall so I assumed that that was still true. However, I don't usually work with Ubuntu so deactivating the firewall is beyond me at the moment.

What did your logs from that server contain? It doesn't seem that the basic troubleshooting techniques will work so digging into the logs would be the next best step.

I don't know if it has logs.
I can give you "/var/log/syslog" as I re-start the program, though.

Jul 21 16:04:51 multiboot motion: [0] Motion terminating
Jul 21 16:04:59 multiboot motion: [0] Processing thread 0 - config file /etc/motion/motion.conf
Jul 21 16:04:59 multiboot motion: [0] Unknown config option "minimum_gap"
Jul 21 16:04:59 multiboot motion: [0] Unknown config option "ffmpeg_filename"
Jul 21 16:04:59 multiboot motion: [0] Processing config file /etc/motion/thread0.conf
Jul 21 16:04:59 multiboot motion: [0] Motion 3.2.9 Started
Jul 21 16:04:59 multiboot motion: [0] Motion running as daemon process
Jul 21 16:04:59 multiboot motion: [0] ffmpeg LIBAVCODEC_BUILD 3352064 LIBAVFORMAT_BUILD 3344896
Jul 21 16:04:59 multiboot motion: [0] Thread 1 is from /etc/motion/thread0.conf
Jul 21 16:04:59 multiboot motion: [1] Thread 1 started
Jul 21 16:04:59 multiboot motion: [0] motion-httpd/3.2.9 running, accepting connections
Jul 21 16:04:59 multiboot motion: [0] motion-httpd: waiting for data on port TCP 8002
Jul 21 16:05:02 multiboot motion: [1] Not a V4L2 device?
Jul 21 16:05:02 multiboot motion: [1] Using VIDEO_PALETTE_YUV420P palette
Jul 21 16:05:02 multiboot motion: [1] Started stream webcam server in port 8001



Also, keep in mind that my LAMPP/XAMPP for Linux does not work either (port 80).

Here it is from that program:

jaredtbrees@multiboot:~$ sudo /opt/lampp/lampp start
Starting XAMPP for Linux 1.6.6...
XAMPP: Starting Apache with SSL (and PHP5)...
XAMPP: Starting MySQL...
XAMPP: Another FTP daemon is already running.
XAMPP for Linux started.
jaredtbrees@multiboot:~$

(It did not output anything to "/var/log/syslog".)

If the LAMPP server is not logging to the main system log then it has it's own log. Searching XAMPP's documentation, I found that there should be logs in the /opt/lampp/logs file. If it is not in that file you will want to consult the LAMPP configuration to determine where the log file is. It's typical for the configuration file to have a line showing where the logs should go.

This is where I got the info for LAMPP: http://www.apachefriends.org/en/faq-xampp-linux.html. Please let me know if you got your LAMPP package from another source so that we can look to them rather than the what I gave you above.

Captured from /opt/lampp/logs/errorlog

[Tue Jul 22 09:22:12 2008] [notice] suEXEC mechanism enabled (wrapper: /opt/lampp/bin/suexec)
[Tue Jul 22 09:22:12 2008] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Tue Jul 22 09:22:12 2008] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?
[Tue Jul 22 09:22:12 2008] [notice] Digest: generating secret for digest authentication ...
[Tue Jul 22 09:22:12 2008] [notice] Digest: done
[Tue Jul 22 09:22:13 2008] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Tue Jul 22 09:22:13 2008] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?
[Tue Jul 22 09:22:13 2008] [notice] Apache/2.2.8 (Unix) DAV/2 mod_ssl/2.2.8 OpenSSL/0.9.8e PHP/5.2.5 mod_apreq2-20051231/2.6.0 mod_perl/2.0.2 Perl/v5.10.0 configured -- resuming normal operations


Have you figured out what is wrong with Motion yet? Can you teach me how to read the logs and troubleshoot?

No, I can't say that I know what's wrong with your installation. Basically, I'm analyzing your logs and searching the Internet for simalar problems and log entries. It seems that you may have the same issue as people at the following forums:

http://www.apachefriends.org/f/viewt...dd271b9eca0fc4
http://nirmaljayasinghe.wordpress.co...heardo-em-boy/

In addition to http://127.0.0.1:8001 and http://127.0.0.1:8002

I would like for your to try...

https://127.0.0.1:8001 and https://127.0.0.1:8002.

Other than pointing you in the direction of other logs and scouring the Internet, I think that I'm out of suggestions on this one without having the computer in front of me to troubleshoot.

I finally figured it out (I think).

I was having issues with the Gnome Settings Daemon after I installed my nVidia driver using EnvyNG, and this was around the time that I started using Compiz-Fusion. This was also around the same time that I got my Ad-Hoc connection working. Therefore, I didn't know which (the Gnome Settings Daemon, EnvyNG, the nVidia driver, Compiz-Fusion, or the Ad-Hoc connection,) was to blame, if any of them.

Well, after a clean install, (this time 64-bit,) I am using Compiz-Fusion and the nVidia driver (not the same as before, but a newer one,) but I am not using Ad-Hoc or EnvyNG.

I have evidence (but not proof) that when EnvyNG installed the nVidia driver, it caused the Gnome Settings Daemon to crash.

My original thought was that it was the Ad-Hoc conncetion, which (in my mind, anyways,) made sense: They both deal with networking.

The only way for me to tell for sure will be to initiate an Ad-Hoc connection using my new installation. I no longer need the Ad-Hoc connection, so it may be a while, if ever. (Actually, within the next few months, I plan to setup Ubuntu in a virtual machine to find out for sure.)

So, I narrowed it down to either the Ad-Hoc connection, or EnvyNG as the culprit.

I will post again when (and if) I find out more.



Thanks gizza23,

computer_freak_8