For future reference, the 30425 is the process ID of the thread reporting the error, and does not indicate the cause of the error, although you can use it to tie together messages from the same thread.
I haven’t tried this. What would be the consequences of deleting/renaming dbinit? My server is already in production and I don’t want to break anything.
After I rename dbinit, do I have to restart the whole server or just the Asterisk service?
No, I mean housing the existing astdb (dbinit is a function from db.c that’s trying to unsuccessfully run and throwing that warning) and letting Asterisk create one from scratch.
The consequences are that any entries you’ve got in astdb would be unavailable.
If this is a production FreePBX system or anything like that, I’d say no, because killing its astdb is disastrous.
[quote=“malcolmd”]No, I mean housing the existing astdb (dbinit is a function from db.c that’s trying to unsuccessfully run and throwing that warning) and letting Asterisk create one from scratch.
The consequences are that any entries you’ve got in astdb would be unavailable.
If this is a production FreePBX system or anything like that, I’d say no, because killing its astdb is disastrous.[/quote]
My mistake, I meant astdb.
Yes, it is a production FreePBX system. So you’re saying I shouldn’t try renaming astdb because my server is on production? What else would you suggest for fixing this issue? What consequences could show in the future if I don’t fix this issue? (Asterisk has been working just fine regardless of the warning messages)
For fixing the issue? Unknown, sorry. I don’t know why Asterisk isn’t able to initialize your astdb. I’ve housed the astdb before on a FreePBX system and had dire (flush it and start over) consequences. So, I do not recommend doing that.
The warning means that Asterisk isn’t able to do anything that involves the astdb, and there’s a lot of stuff in FreePBX that writes to and reads from the astdb. So, while things are working, there are probably other things that aren’t working.
[quote=“malcolmd”]For fixing the issue? Unknown, sorry. I don’t know why Asterisk isn’t able to initialize your astdb. I’ve housed the astdb before on a FreePBX system and had dire (flush it and start over) consequences. So, I do not recommend doing that.
The warning means that Asterisk isn’t able to do anything that involves the astdb, and there’s a lot of stuff in FreePBX that writes to and reads from the astdb. So, while things are working, there are probably other things that aren’t working.[/quote]
My asterisk server is running on a VM so I will try renaming astdb and then rebooting the server. I will take a snapshot so I can restore the VM in case I break it.
I will let you know if it worked. Thanks for your help and guidance!