[Kurt H.]

Hello Eric

I tried to install the new version on my raspberry pi. Everything seemed to work, but finally Docker run into an error. It seems like there's a problem with the container "ticketscad_db", see below.

+] up 19/19king to docker.io/library/ticketscad-newui:local                                                                                                                                                                            42.9s
 ✔ Image mariadb:11              Pulled                                                                                                                                                                                                  75.6s
 ✔ Image ticketscad-newui:local  Built                                                                                                                                                                                                 1012.3s
 ✔ Network ticketscad_default    Created                                                                                                                                                                                                  0.4s
 ✔ Volume ticketscad_app_keys    Created                                                                                                                                                                                                  0.0s
 ✔ Volume ticketscad_db_data     Created                                                                                                                                                                                                  0.0s
 ✔ Volume ticketscad_app_uploads Created                                                                                                                                                                                                  0.0s
 ✔ Volume ticketscad_app_cache   Created                                                                                                                                                                                                  0.0s
 ✘ Container ticketscad_db       Error dependency db failed to start                                                                                                                                                                     51.8s
 ✔ Container ticketscad_newui    Created                                                                                                                                                                                                  0.7s
dependency failed to start: container ticketscad_db is unhealthy
hb9be@EmmeCAD:~/ticketscad $ run ticketscad

Any Idea what I can do?

Thanks!

BR

Kurt

[Eric Osterberg]

Hi Kurt,

Good news — that message doesn't mean TicketsCAD itself failed. It means the database container stopped before it finished starting up, so the app refused to start without it. The compose summary can't tell us why the database stopped; this command will:

docker compose logs db

On a Raspberry Pi, it's almost always one of three things:

1. Out of memory. MariaDB gets killed by the Pi — often because the app image was still building at the same time (that build is heavy and took about 17 minutes on your Pi, which is a sign it was starved for resources). Check with: free -h
   Fixes: add a little swap (a 2 GB swapfile is plenty), or do it in two steps so the build and the database don't compete: docker compose build then docker compose up -d
   1 GB Pis are very tight; 2 GB or more is comfortable.
2. A 32-bit operating system. MariaDB 11 only comes in 64-bit. Check with: uname -m
   You want it to say aarch64. If it says armv7l, you're on 32-bit Raspberry Pi OS and would need the 64-bit version.
3. A half-finished database from the first failed run. Start clean (safe on a first install, it just wipes the empty database): docker compose down -v then docker compose up -d

Personally, the Pi is a pretty weak 'server', has limited i/o, cpu, and ram. On top of that is a less popular architecture, using arm instead of the common intel and AMD instruction sets. I think there are plenty of alternative mini computers on the market that might be a better fit as TicketsCAD increases its capabilities and uses code and libraries that are current technologies, rather than the code that is now more than 20 years ago.

If you paste here the last 30 or so lines of "docker compose logs db", we can hopefully tell exactly which issue it is.

73,
Eric

--
You received this message because you are subscribed to the Google Groups "Open Source CAD" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-source-c...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/CAGVvMhqm2ZanQGg7hh_p7bBvRGzPz1SHroiMzdaP1EbCvi4-jQ%40mail.gmail.com.

[Gerald Hurt]

I will say that TicketsCAD does run okay on a Pi5 (4G memory) using Apache/php/MariaDB (not docker). Fine for testing but once a load is put on it I’m pretty sure performance will drop significantly.

Jay

[Kurt H.]

Hi Eric

You're right, the performance of the pi was not good enough. I keep it for other projects.

But now I changed to a much faster tiny PC running Ubuntu and still no success. I installed PHP and apache  and get its welcome page at http://localhost . Then I followed your instructions for docker install. This time all messages are green, the container is started but: no ticketscad page on localhost:8080, localhost/ticketscad, localhost/ticketscad_newui...what the heck am I doing wrong?

I'm usually not a Linux guy so please foregive my beginner questions...

Thanks!

Kurt

To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/CAJLaYFXNYxSU%3DqSc_aQE-Ciu-oEt5L%2BtD3twXBH23aXxxJwLcg%40mail.gmail.com.

[Eric Osterberg]

Hi Kurt,

Good news - nothing is broken. It is running; you are just knocking on the wrong door.

The main thing is the address. A Docker install of TicketsCAD opens at this exact address:

http://localhost:8081

That number after the colon, 8081, is called a "port." It is not 8080, and it is not a folder name like /ticketscad. The whole app lives at that one address. So localhost/ticketscad and localhost/ticketscad_newui will never work - those "ticketscad" names you saw are the internal names Docker gives the containers, not web addresses. Open http://localhost:8081 and you should see the TicketsCAD login page.

That welcome page you saw at plain http://localhost is a separate thing - it is Ubuntu's own Apache web server saying hello, not TicketsCAD. You actually did not need to install Apache or PHP yourself for the Docker route, because Docker already includes them inside the container. It is harmless, so you can leave it; just don't mistake it for TicketsCAD. TicketsCAD is on :8081.

When you reach the login page you will need the first-time admin password. It is printed in the startup log. From the folder where you ran the docker commands, run:

docker compose logs app | grep -i password

And please do not apologize - these are exactly the right questions, and you are not doing anything wrong. To make the whole picture click, I wrote a short plain-English guide for people coming to this without a Linux or web background - what the app is, how to open it, the port-versus-folder thing, and a few free links for learning the basics. It is here:

https://github.com/openises/TicketsCAD/blob/main/docs/GETTING-STARTED-FOR-BEGINNERS.md

One thing worth knowing now so it is not a surprise later: with Docker, keeping it updated is not just "git pull." Because the app is built into the Docker image, you update by pulling the new code and then rebuilding. From your ticketscad folder:
git pull
docker compose up -d --build
The rebuild (the --build part) is the important bit - it is what actually applies the update, and the container handles the database changes on its own when it restarts. Back up first; the full step-by-step is in the Upgrading section of the Docker guide:
https://github.com/openises/TicketsCAD/blob/main/docs/DOCKER.md
Open http://localhost:8081 and let me know if the login page comes up.
73,
Eric

To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/CAGVvMhoo4BUa90FR0VUSKyhDTTYdAxsMrhzUJ78eyf_Qc0pyaw%40mail.gmail.com.

[Kurt H.]

Hi Eric,

of course, knocking at the right door did the trick. Now I feel like David Bowie ... I'm an absolute beginner :-)

Meanwhile I could log in, create users, did a lot of customizing settings and create my first incident. So far the translation to German looks fine to me.

Now my next question. In my scenario I'd like to have the OSM map offline available, it looks like this isn't too complicated to do. Obviously I need a tile server, which should be running in docker. Like 

overv/openstreetmap-tile-server - Docker Image

Do you know if this one's a good choice? or do you recommend another one or even a different way to reach my goal?

Thanks and have a good start of the week!

Best 73s

Kurt

To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/CAJLaYFUubBgSAhWpEC_LaJGcern3fgvBkOUhiYd5Nht7y4VHLQ%40mail.gmail.com.

[Eric Osterberg]

The system supports caching of maps to ensure high availability in the event that the map server is offline or unreachable. 

You mentioned your goal is offline maps? Can you expand on your requirements a little? 

Do they need to be strictly offline for a particular purpose?

To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/CAGVvMhoNELV%3DC4enbrGPXT%2B9hQMWx1-zvGah7dOdaJ7tUP0WEw%40mail.gmail.com.

[Kurt H.]

Hi Eric,

Our amateur radio club supports the regional emergency management agency. We operate an AREDN network that functions largely independently of the power grid and is used by the emergency management as "last way of communication", if, for example, during a blackout the internet and all fixed and mobile phones are dead. That's why we'd also like to have the maps available offline - else, no power, no internet, no maps.

The scope of this regional emergency management agency has been expanding in recent months, and Incidents in more and more towns and cities are now being coordinated from our “home base.” Today, If an incident occurs in the neighboring town X, it is (really!!) recorded on paper only. If the same incident is reported 10 minutes later directly to us, we are unaware of it and, in the worst-case scenario, end up alerting other emergency responders for it, because the other ones in the city X seem to be busy already...they do not reply and we don't know they are already on the scene or somewhere else. That is why we have come up with the idea of introducing Tickets CAD as a solution to this problem.

How does this "caching" work? 

Thanks a lot!

Kurt

To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/CAJLaYFW%2BZaSptknxW%2Bb8Ev-3w-EvQ7p6m_z4qoUTjrOE9UqK%2BA%40mail.gmail.com.

[Eric Osterberg]

To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/CAGVvMhrhR5WQu_-_TttuQs-bHeCEuk%3Dpa3OPc3iERQy1wLJ2jA%40mail.gmail.com.