Ubuntu 24.04 and Zoneminder install

[mikb]

Are you doing the install as root? Do you do "sudo su" and get a prompt for a password?

Any install on Linux needs to be done as root which is the administrator. Maybe that is why your commands are4 failing.

"TimeoutError: [Errno 110] Connection timed out"

Never mind being root (which probably does help massively) ... "do you have working internet access?" is my thought at seeing that.

@bbunge it looks like "add-apt-repository ppa:iconnor/zoneminder-1.36" is expecting to make a connection to something remotely, and is not able to do so. So either you have no working internet, a firewall that's blocking you, or something is down ...

[pd2eds]

I use sudo su
So as root
See
root@edwin-450-101nd:/home/edwin#
I understand that you want to help.
My thanks for that.
But I don't understand why it doesn't work either.
Have reinstalled Ubuntu so many times, and always a blank screen.
Always format the HDD so that nothing is left behind.
I didn't put anything else on it before I put it on. So a clean Ubuntu.
But things already go wrong with add-apt-repository ppa:iconnor/zoneminder-1.36.
I don't understand how things are going well for you. I also tried Ubuntu 22.04. doesn't work either.
I did have it on 22.04, but because the PC crashed I was forced to reinstall Ubuntu.

I do have an internet connection.
Can simply update and upgrade.
Everything else works here.
I haven't thought about a firewall. Then I'll have to find out what's going on.

[pd2eds]

Quick update.
How is it possible.
A month ago I received a new internet router from my internet provider.
Simply connect this and follow the instructions. Nothing else.
Now I read from MIKB that firewall may have something to do with this.
Just turned this off and again and

Tried add-apt-repository ppa:iconnor/zoneminder-1.36.

And yes, right data.
Tomorrow I will first provide the PC with a clean Ubuntu and install zoneminder. That should work out fine.
As soon as it's successful I'll let you know.
You are smart people.

[cookiemonster]

probably the pc had no DNS or no gateway configured correctly or both. A typical result of router change when the clients haven't been "made aware" by restarting their dhcp clients.

[mikb]

A month ago I received a new internet router from my internet provider.
Simply connect this and follow the instructions. Nothing else.

Yes. I love the simplicity of things like this. "Don't worry, it will just work!" -- and I'm never surprised to find that _something_ breaks!

And yes, right data.
Tomorrow I will first provide the PC with a clean Ubuntu and install zoneminder. That should work out fine.
As soon as it's successful I'll let you know.
You are smart people.

You learn from years of stuff going wrong, finding out _why_, and then fixing it. One step at a time. You can't fix everything at once, and when "everything is broken!" comes down to one particular failure, fixing that one failure in the sea of failures can clear a _lot_ of problems out of the way.

If your computer can't see the site to install things from, then they don't get installed. Nothing you do after that will make any difference, zoneminder isn't there, and can't be convinced to work. I can see why that would be disheartening!

People who get into coding/programming get overwhelmed by the pages and pages of error after error after error when compiling something. Most of the errors are the compiler repeatedly smashing its teeth out as it falls repeatedly downstairs, because it tripped over on a single misplaced ';' somewhere.

The first error is always the one to look at, because that was the _cause_, everything else cascades from that.

I'm glad your at least up and fighting again!

[pd2eds]

Good luck yesterday, but today I installed a clean Ubuntu 24.04 and tried to install it.
Yet still there
add-apt-repository ppa:iconnor/zoneminder-1.36 that it doesn't go any further.
Yesterday I was shown data, but not today.
Firewall is turned off. I don't know about DNS and Gateway. I don't understand that yet. I'll have to find out how that works.
I have never changed this. Had high hopes today, but unfortunately no luck today.

Today I bought a recorder for the camera. If in the future I have a PC that crashes again and I have to reinstall it, I will get even more gray hairs. It would have been nice if I had managed it, but unfortunately no success with zm. I also don't know much about changing things in the router. This is also too complicated for me. Thank you everyone for your input and have fun with Zoneminder.

[bbunge]

Not a good idea to turn off a firewall! Worse than going outside in the winter with no pants...

Maybe the new router from the ISP is borked. I use my own router that way I control my network!

[cookiemonster]

So this is ubuntu, right?
let's go from the top, to see how is doing its network things. Commands from $ are as normal user, from # are from elevated (root) or sudo.
let's find out its ip address:

Code: Select all

$ip a

this ip address needs to be in the range of your router. You can log in to your router admin pages to verify is in the correct range. If not, it needs to get one. How to do it without having to reboot is depending on ubuntu versions that we can get to.
Meantime we also need to know if it has the correct other network settings ie. gateway, and dns server.
Please show result of:

Code: Select all

$ip route

The normal routine is that when you boot the machine, it queries the network it is connected to (via a cable for instance), and get these details back from the router that serves that network, and configure itself with them.
If this fails, you have "no internet" or "no network". So we're looking to see what is has.
One more thing whilst you're at it, check name resolution aka DNS.

Code: Select all

$dig example.com

[pd2eds]

I turned the Firewaal back on. I'm starting to understand it all less and less.
So turn off the firewall and turn it back on again.
I don't understand the terms ip a ip route dig example.com at all. I see a lot of numbers but they mean nothing to me.
I have little idea about that. Maybe simple for you, but too complicated for me...
But if add-apt-repository ppa:iconnor/zoneminder-1.36 already gives problems, then I don't know what else.
The router is not broken. I can do everything with it. I can also log in via the camera app. Also from outside.
I have never changed settings in the router.
I don't understand many terms.
You can't understand everything.
All good intentions from you.
I don't think we can get any further with zoneminder.
Here are the details of the commands

I really don't know what it all means??????

ip a

edwin@edwin-450-101nd:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 74:85:2a:1c:77:c2 brd ff:ff:ff:ff:ff:ff
altname enp3s0
inet 192.168.1.118/24 brd 192.168.1.255 scope global dynamic noprefixroute eno1
valid_lft 78597sec preferred_lft 78597sec
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 60:6d:c7:6d:e2:35 brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 96:65:8f:62:81:60 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever


ip route

edwin@edwin-450-101nd:~$ ip route
default via 192.168.1.1 dev eno1 proto dhcp metric 100
169.254.0.0/16 dev eno1 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.118 metric 100

dig example.com

edwin@edwin-450-101nd:~$ dig example.com

; <<>> DiG 9.18.30-0ubuntu0.22.04.2-Ubuntu <<>> example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1866
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;example.com. IN A

;; ANSWER SECTION:
example.com. 1 IN A 96.7.128.198
example.com. 1 IN A 96.7.128.175
example.com. 1 IN A 23.192.228.80
example.com. 1 IN A 23.215.0.136
example.com. 1 IN A 23.215.0.138
example.com. 1 IN A 23.192.228.84

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Fri May 09 18:10:55 CEST 2025
;; MSG SIZE rcvd: 136

[cookiemonster]

This looks good. You'll start understanding bit by bit. I'll highlight what this has told us:

I turned the Firewaal back on. I'm starting to understand it all less and less.
So turn off the firewall and turn it back on again.
I don't understand the terms ip a ip route dig example.com at all. I see a lot of numbers but they mean nothing to me.
I have little idea about that. Maybe simple for you, but too complicated for me...
But if add-apt-repository ppa:iconnor/zoneminder-1.36 already gives problems, then I don't know what else.
The router is not broken. I can do everything with it. I can also log in via the camera app. Also from outside.
I have never changed settings in the router.
I don't understand many terms.
You can't understand everything.
All good intentions from you.
I don't think we can get any further with zoneminder.
Here are the details of the commands

I really don't know what it all means??????

ip a

edwin@edwin-450-101nd:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 74:85:2a:1c:77:c2 brd ff:ff:ff:ff:ff:ff
altname enp3s0
inet 192.168.1.118/24 brd 192.168.1.255 scope global dynamic noprefixroute eno1
valid_lft 78597sec preferred_lft 78597sec
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 60:6d:c7:6d:e2:35 brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 96:65:8f:62:81:60 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever


ip route

edwin@edwin-450-101nd:~$ ip route
default via 192.168.1.1 dev eno1 proto dhcp metric 100
169.254.0.0/16 dev eno1 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.118 metric 100

dig example.com

edwin@edwin-450-101nd:~$ dig example.com

; <<>> DiG 9.18.30-0ubuntu0.22.04.2-Ubuntu <<>> example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1866
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;example.com. IN A

;; ANSWER SECTION:
example.com. 1 IN A 96.7.128.198
example.com. 1 IN A 96.7.128.175
example.com. 1 IN A 23.192.228.80
example.com. 1 IN A 23.215.0.136
example.com. 1 IN A 23.215.0.138
example.com. 1 IN A 23.192.228.84

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Fri May 09 18:10:55 CEST 2025
;; MSG SIZE rcvd: 136

This machine has a network interface named eno1 and also with an alias of enp3s0 with a status of UP. So it is connected to a network via it.
It has an ip address of 92.168.1.118 . Other attributes are normal like the broadcast address in its scope. Incidentally but not a problem, there is a wifi interface not connected to anything (best like that for now), and at some point you installed docker.
Then "default via 192.168.1.1 dev eno1 proto dhcp metric 100" tells us that the machine's default route (its way to "connect" out of itself) is via 192.168.1.1 . This must be the ip address of your gateway to the world, which is your router.
So, when it needs to go to an address NOT in its (your) house network (192.168.1.1/24) it will use 192.168.1.1 as the "door" out. As we said this MUST be your router. It follows that if you were to change router for instance, either the new router has to be setup with that address or your machine needs to also be changed to use the new gateway. So far so good.
The last part is your dig command. I was worried that it wasn't available in your machine but it is. It tells "hey DNS server, what is the ip I must use if I wanted to talk to example.com?". If you get an ip -and there is more than one that can be used in this case-, then it has what it needs.
All this is as we want and is healthy from the networking point of view.

So let's try it again:
If as edwin:
Edit: from the docs, do first:

Code: Select all

$sudo apt install -y software-properties-common

Then:

Code: Select all

$sudo add-apt-repository ppa:iconnor/zoneminder-1.36

but check just before it that you can get another successful result from dig example.com . Just to rule out infrequent dns failures.

[adam.robertson]

You could possibly pay for some help from the Zoneminder guy(s):
https://cloud.zoneminder.com/services.html

They do remote assistance. It might be worth some dollars just to get a good basic setup.

[pd2eds]

First sudo apt install -y software-properties-common

Then sudo add-apt-repository ppa:iconnor/zoneminder-1.36

Then I get
TimeoutError: [Errno 110] Connection timed out

Installing zoneminder-1.36 still fails.

Thanks for the explanation cookiemonster, but don't understand it completely.
Still too complicated for me all those numbers, and too much machine language


Then I went searching on the web.
This is what I found.
I thought I'd give it a try.
I don't know what it means, but I executed it.

sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=1

Then again
sudo add-apt-repository ppa:iconnor/zoneminder-1.36

And zoneminder started installing. I haven't done anything else yet, and I'm just waiting to see what else I have to do.

[pd2eds]

Tried again to get it working.
Finally after attempt 3 I managed to get it working.
I had tried this site https://zoneminder.readthedocs.io/en/st ... 2-04-jammy several times but without success, until today. The PC is equipped with Ubuntu 24.04, but I followed the instructions for Ubuntu 22.04 anyway.
It worked.
I don't know if
sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=1 had anything to do with it.
I have already added the camera in zm and I have an image.
Now change the language to Dutch so I can understand it a bit better.
Not an easy program to install.
So far the update.

[cookiemonster]

You've done well there.
I have only worked with IPv4. I am of the opinion that IPv6 is a royal pain in the back. I disable it everywhere in my network.
I know I am in a dinosaur meantality minority and should get with the times but I just can't get on with IPv6. Necessary but badly architected in my opinion. Rant over.
pd2eds, if your network is IPv4 which is determined by your gateway/router, then devices using IPv6 _can_ get confused, as you have experienced.
Most just get a link local address and continue happily living in IPv4 land but some struggle.
Also MTU fragmentation can show these symptoms (I forgot, should have suggested a way to check), especially when your ISP uses PPoE and/or VLANs over PPoE. Horrible but quite commo in Europe.

[pd2eds]

Thank you for your messages.
Help is always good.
Hopefully everything will continue to run smoothly again.
I can further provide the PC with other software programs.