Forums WoW Modding Support Archives Azerothcore Discord Archives [DiscordArchive] running a classic install and trying to have my world and auth servers start up on boot. I've opted

[DiscordArchive] running a classic install and trying to have my world and auth servers start up on boot. I've opted

[DiscordArchive] running a classic install and trying to have my world and auth servers start up on boot. I've opted

rektbyfaith
Administrator
0
01-28-2023, 08:47 PM
#1
Archived author: Ninjaro • Posted: 2023-01-28T20:47:04.988000+00:00
Original source

running a classic install and trying to have my world and auth servers start up on boot. I've opted to put them in my cron as @reboot entries each with a bash script that basically just calls 'screen -dmS world ./worldserver' and similar for authserver. However when I load the wow client and try to login, it accepts my creds as usual but just hangs on the Authenticating dialog. If I kill the authserver process and restart it manually it gets past that and hangs on the Connected dialog but doesn't connect to my realm. Same story if I kill the worldserver and start again manually then it all works fine. Is this something somebody is already familiar with? What am I missing here?
rektbyfaith
01-28-2023, 08:47 PM #1

Archived author: Ninjaro • Posted: 2023-01-28T20:47:04.988000+00:00
Original source

running a classic install and trying to have my world and auth servers start up on boot. I've opted to put them in my cron as @reboot entries each with a bash script that basically just calls 'screen -dmS world ./worldserver' and similar for authserver. However when I load the wow client and try to login, it accepts my creds as usual but just hangs on the Authenticating dialog. If I kill the authserver process and restart it manually it gets past that and hangs on the Connected dialog but doesn't connect to my realm. Same story if I kill the worldserver and start again manually then it all works fine. Is this something somebody is already familiar with? What am I missing here?

rektbyfaith
Administrator
0
01-28-2023, 08:48 PM
#2
Archived author: Ninjaro • Posted: 2023-01-28T20:48:24.356000+00:00
Original source

everything looks the same in both scenarios, I can see the same ports listening, the daemons are running using the same user.
rektbyfaith
01-28-2023, 08:48 PM #2

Archived author: Ninjaro • Posted: 2023-01-28T20:48:24.356000+00:00
Original source

everything looks the same in both scenarios, I can see the same ports listening, the daemons are running using the same user.

rektbyfaith
Administrator
0
01-28-2023, 08:50 PM
#3
Archived author: Revision • Posted: 2023-01-28T20:50:40.098000+00:00
Original source

There are issues using cron to automatically start it. You might get around it by adding a delay. I don't think a solution was ever shared or discovered but it's worth a try.
rektbyfaith
01-28-2023, 08:50 PM #3

Archived author: Revision • Posted: 2023-01-28T20:50:40.098000+00:00
Original source

There are issues using cron to automatically start it. You might get around it by adding a delay. I don't think a solution was ever shared or discovered but it's worth a try.

rektbyfaith
Administrator
0
01-28-2023, 08:53 PM
#4
Archived author: Ninjaro • Posted: 2023-01-28T20:53:46.080000+00:00
Original source

gotcha ok. I see the db isn't up quick enough, but because they both wait and try again I figured thats ok at least. I'll try some other options, thank you
rektbyfaith
01-28-2023, 08:53 PM #4

Archived author: Ninjaro • Posted: 2023-01-28T20:53:46.080000+00:00
Original source

gotcha ok. I see the db isn't up quick enough, but because they both wait and try again I figured thats ok at least. I'll try some other options, thank you

rektbyfaith
Administrator
0
01-28-2023, 08:54 PM
#5
Archived author: Revision • Posted: 2023-01-28T20:54:42.622000+00:00
Original source

Try adding a delay to the start and see if that fixes it.
rektbyfaith
01-28-2023, 08:54 PM #5

Archived author: Revision • Posted: 2023-01-28T20:54:42.622000+00:00
Original source

Try adding a delay to the start and see if that fixes it.

rektbyfaith
Administrator
0
01-28-2023, 08:59 PM
#6
Archived author: Ninjaro • Posted: 2023-01-28T20:59:57.222000+00:00
Original source

well I'll be.... that worked
rektbyfaith
01-28-2023, 08:59 PM #6

Archived author: Ninjaro • Posted: 2023-01-28T20:59:57.222000+00:00
Original source

well I'll be.... that worked

rektbyfaith
Administrator
0
01-28-2023, 09:00 PM
#7
Archived author: Ninjaro • Posted: 2023-01-28T21:00:28.073000+00:00
Original source

20 seconds. I wonder if its something to do with the network stack not being ready so it can't bind the ports/processes properly or something
rektbyfaith
01-28-2023, 09:00 PM #7

Archived author: Ninjaro • Posted: 2023-01-28T21:00:28.073000+00:00
Original source

20 seconds. I wonder if its something to do with the network stack not being ready so it can't bind the ports/processes properly or something

rektbyfaith
Administrator
0
01-28-2023, 09:01 PM
#8
Archived author: Ninjaro • Posted: 2023-01-28T21:01:03.746000+00:00
Original source

thanks for the tip!
rektbyfaith
01-28-2023, 09:01 PM #8

Archived author: Ninjaro • Posted: 2023-01-28T21:01:03.746000+00:00
Original source

thanks for the tip!

rektbyfaith
Administrator
0
01-28-2023, 09:02 PM
#9
Archived author: Revision • Posted: 2023-01-28T21:02:17.684000+00:00
Original source

Great!
rektbyfaith
01-28-2023, 09:02 PM #9

Archived author: Revision • Posted: 2023-01-28T21:02:17.684000+00:00
Original source

Great!

Recently Browsing
 1 Guest(s)
Recently Browsing
 1 Guest(s)