Error Loggin into Log4omV2 with MySQL DB

Post Reply
N3AIR
Novice Class
Posts: 15
Joined: 26 May 2023, 16:27

Error Loggin into Log4omV2 with MySQL DB

Post by N3AIR »

We just setup a multi-station off Log4OMV2 using MySQL. JTAlert will talk to MySQL via the test. But can not log the QSO. I have used the same settings as I have many times over when using SQLite on a single computer. I have found some old articles around this error but nothing recent. I don't know which side the issue is on here but any help will be appreciated.
error1.png
error1.png (9.86 KiB) Viewed 489 times
error2.png
error2.png (19.18 KiB) Viewed 489 times
error3.png
error3.png (30.25 KiB) Viewed 489 times
N3AIR
Novice Class
Posts: 15
Joined: 26 May 2023, 16:27

Re: Error Loggin into Log4omV2 with MySQL DB

Post by N3AIR »

error4.png
error4.png (24.69 KiB) Viewed 488 times
User avatar
G4POP
Log4OM Alpha Team
Posts: 10748
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Error Loggin into Log4omV2 with MySQL DB

Post by G4POP »

Have you asked this question of JTAlert? as it seems more on their side than Log4OM
73 Terry G4POP
N3AIR
Novice Class
Posts: 15
Joined: 26 May 2023, 16:27

Re: Error Loggin into Log4omV2 with MySQL DB

Post by N3AIR »

I have, current thought is UDP issue into Log4om and/or something to do with MySQL. Going to setup the computer to user SQLite instead of MySQL for testing and see if it works without issue.
User avatar
G4POP
Log4OM Alpha Team
Posts: 10748
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Error Loggin into Log4omV2 with MySQL DB

Post by G4POP »

Unless you have special requirements SQLITE is fine for up to about 130k QSO's
73 Terry G4POP
N3AIR
Novice Class
Posts: 15
Joined: 26 May 2023, 16:27

Re: Error Loggin into Log4omV2 with MySQL DB

Post by N3AIR »

We are using MySQL for multiple computers and putting data into our website. The issue ended up being using another port from 2236 to make it work. The port is not in use anywhere but after trying to change the DB type and reconfiguring everything several times, ended up changing the port to fix it.
Post Reply