Acars closed - pirep not cancelled or continued.

[dougjuk]

Acars closed - pirep not cancelled or continued.

Ok this has been a problem for me for a long time, one of my users constantly just leaves Acars running with the flightsim closed. Or he shuts the computer down without closing Acars or cancelling the flight.

If he has a crash he does not restart and deal with the pirep either. In fact he seems to be very clever at screwing things up big time. Just ask Dispo.

I often see part deleted flights in the database which I have to clear up as the system seems to ignore them. (cron is working fine)

I also often see error messages in the laravel log caused by him. I can trace it to his api code and his IP address in norther Germany.

In an incident yesterday I don't know how but I ended up with 97000 entries in the laravel log concerned with him and his link to the site from Acars. This lead to a larval log of 5 gig and a backup of over 300 meg going to the offsite storage. The last incident a few days ago I had a laravel log at 1.59 gig.

So I would like the ability to switch a user off from using Acars.

I would also like the function that if Acars is closed without filing or cancelling the flight that the flight be automatically cancelled. Allowing a short time for a possible continuation if Acars was closed or crashed.

This particular problem with this user has been going on since we started with phpvms (2020) but I have managed it so far. I have written to and spoken to the user many times advising the correct use of Acars. But he forgets and continues to cause issues.

I have banned him today from using Acars until I can be certain that this log issue can be avoided.

many thanks

Doug

[dougjuk]

From Nabeel

I can add some additional logging to say when the last update i have is, that'll give some sense of the time from the last time there was data.

[dougjuk]

Our VA board had a chat, we thought that when you close Acars we would like the option to delete the flight.

Uli despite being told many times thinks the flight auto deletes. The problem is that the site does delete it (set to 1 hour) and he then reopens and causes errors. Most the time it is no issue but for some reason this version repeated over and over causing the massive sized log file.