Are there currently problems with the accounting servers?

General Discussion
1

hello everyone, for a few hours I’ve been getting the error message that the accountig servers are not available. firewall is enabled for port 2008. here is an excerpt from the log:

2022-06-02T14:06:24+02:00 TS |INFO | | |failed to download accounting revocation list - count: 5

2022-06-02T13:06:24+02:00 TS |INFO | | |failed to download accounting revocation list - count: 4

2022-06-02T12:06:24+02:00 TS |INFO | | |failed to download accounting revocation list - count: 3

2022-06-02T11:06:24+02:00 TS |INFO | | |failed to download accounting revocation list - count: 2

1 Like
2

Got the same thing here. Will talk to our IT.

2 Likes
3

OK. thanks.

4

Just as an update.

We are going to fix this.
Meanwhile nothing bad will happen with Accounting. So For now the error can be ignored.

4 Likes
5

can you also ignore this if the accounting message appears in the server log?

6

Yes.

7

Ok. Thanks.
it’s not gone yet. still the error message.

8

Just ignore it. As said before.

3 Likes
9

But it seems to work every now and then :slight_smile: - or am I wrong?

2022-06-04T11:06:26+02:00 TS |INFO | | |failed to download accounting revocation list - count: 50
2022-06-04T10:06:26+02:00 TS |INFO | | |failed to download accounting revocation list - count: 49
2022-06-04T10:06:23+02:00 TS |INFO | | |successfully downloaded revocation list for myteamspeak id
2022-06-04T09:06:26+02:00 TS |INFO | | |failed to download accounting revocation list - count: 48
2022-06-04T08:06:26+02:00 TS |INFO | | |failed to download accounting revocation list - count: 47
------------
2022-06-03T10:06:24+02:00 TS |INFO | | |failed to download accounting revocation list - count: 25
2022-06-03T10:06:23+02:00 TS |INFO | | |successfully downloaded revocation list for myteamspeak id
2022-06-03T09:06:24+02:00 TS |INFO | | |failed to download accounting revocation list - count: 24
10

Recently I noticed since 2022-06-01 my server shows an error on the logs
ServerLibPriv | |failed to download revocation list - count: 1

and I checked my server which has connectivity to ts3services.teamspeak.com on port 443 but I was wondering about running nginx and apache2 on the same server as TS3 can it cause that error and also in general how I can figure out why that’s happening

11

Hey,

There was a Problem in last 2 days look here

The showed Error in the Server log can be ignored. :slight_smile:

It should be resolved. :slight_smile:

1 Like
12

Oh, ok pew I was like I broke something XD ty

1 Like
13

My server log is shows nothing anymore about that error :slight_smile:

14

That’s nice, it’s different for me:

2022-06-09T06:07:14+02:00 TS |INFO | | |failed to download accounting revocation list - count: 165

2022-06-09T05:07:14+02:00 TS |INFO | | |failed to download accounting revocation list - count: 164

2022-06-09T04:07:14+02:00 TS |INFO | | |failed to download accounting revocation list - count: 163

2022-06-09T03:07:14+02:00 TS |INFO | | |failed to download accounting revocation list - count: 162

2022-06-09T02:07:14+02:00 TS |INFO | | |failed to download accounting revocation list - count: 161

2022-06-09T01:07:14+02:00 TS |INFO | | |failed to download accounting revocation list - count: 160

2022-06-09T00:07:14+02:00 TS |INFO | | |failed to download accounting revocation list - count: 159

2022-06-08T23:07:14+02:00 TS |INFO | | |failed to download accounting revocation list - count: 158

It’s up-to-date from the client, but I think it will be the same.

15

I had this problem on two of my servers.
And BOTH of them just died. pid file stayed there and they apparently just killed themselves, in the middle of the night.
This was the last log entry on the first server

2022-06-14 10:59:41.766961|INFO    |ServerLibPriv |   |failed to download revocation list - count: 105
2022-06-14 11:58:08.622896|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2022-06-14 13:59:41.824610|INFO    |ServerLibPriv |   |failed to download revocation list - count: 106
2022-06-14 16:59:41.890147|INFO    |ServerLibPriv |   |failed to download revocation list - count: 107
2022-06-14 19:59:41.938521|INFO    |ServerLibPriv |   |failed to download revocation list - count: 108
2022-06-14 22:59:41.982860|INFO    |ServerLibPriv |   |failed to download revocation list - count: 109

At about 3 in the morning I was called that our server is down.
And this is the log of my second server

2022-06-14 11:30:54.108978|INFO    |ServerLibPriv |   |failed to download revocation list - count: 38
2022-06-14 14:30:54.276802|INFO    |ServerLibPriv |   |failed to download revocation list - count: 39
2022-06-14 17:30:54.385257|INFO    |ServerLibPriv |   |failed to download revocation list - count: 40
2022-06-14 20:30:54.489392|INFO    |ServerLibPriv |   |failed to download revocation list - count: 41
2022-06-14 23:30:54.618454|INFO    |ServerLibPriv |   |failed to download revocation list - count: 42
2022-06-15 02:30:54.734159|INFO    |ServerLibPriv |   |failed to download revocation list - count: 43
2022-06-15 05:30:54.852202|INFO    |ServerLibPriv |   |failed to download revocation list - count: 44
2022-06-15 07:57:56.407307|ERROR   |Accounting    |   |failed to register local accounting service: Ungültiger Dateideskriptor

I’m taking pride in having high uptimes on my server. One was running since february 2021 with zero downtime, until this :cry:

16

This error has nothing to do with revocation list.

4 Likes
17

Hi,

did you solve the problem or is it solved?
I have the same Problem.

The Servertime is synced, i took a Backup of the Server and set it up again, i took a complete new ts3server.sqlitedb.
I had a Non-Profit Licence and took a Gamer License.

Nothing worked.

The Server is a Debian GNU/Linux Bullseye (all Packages actual) and parallel it is only a Mumble Server installed, nothing else.

Is there still a Problem with

2022-06-28 12:42:10.586829|INFO    |ServerLibPriv |   |failed to download revocation list - count: 1
18

Hi,

o.K., this Message i didn’t read.