Huge log file : prod.deprecations.log

Chabi02 · 30 December 2024 09:16

Many thanks for this, I will try when I’ll go back.

Again, thanks a lot for this !

I wish to all a happy and great new year 2025 (some hours before !!!)

Best wishes,
Xavier

Chabi02 · 6 February 2025 15:24

Hi Farstar,
Back after a while, I have upgraded to SuiteCRM 8.8 and to finalize this, tried to run your trick.

First, my monolog.yaml is in config/packages directly (no “prod” folder).
I dont even find the filter you are talking to.

Then if I run the bin/console cache:clear, I can see on a green background “OK Cache for the “prod” environnement (debug=false was successfully cleared”.
But If I check the logs/prod/prod.deprecations.log, the size is still the same (…29.7 Gb !!!).

What did I miss ?
Thanks for your help
Xavier

Farstar · 10 February 2025 17:29

Does it keep growing up with “php.INFO: User Deprecated” messages?

rsp · 10 February 2025 17:50

What SuiteCRM version you’re using?

Chabi02 · 11 February 2025 08:32

Hi,.
I’m using 8.8.0 (very last one).
Farstar, I can even not open the file as 29.7Gb to edit is too big…
And as I already tried to remove the file and this seems to “block” the CRM, I am still stuck with this…

Thanks for your help,
Xavier

pgr · 11 February 2025 10:52

@Chabi02 you have to access the file from the operating system and delete it or trim it there.

Just remove it from Linux

Chabi02 · 11 February 2025 11:08

Hi Pgr
I already did this in the past (tried to delete the file) : if I remove the prod.deprecations.log, just after that, some CRM screens does not work anymore (studio, repair and rebuild, etc…), even if I add again an empty file with the same name and the correct rights…

pgr · 11 February 2025 12:37

That doesn’t make much sense. Maybe try again, this time shutdown the web server before deleting the file. Then do a Symfony cache clear and restart the server.

And make sure you get those ownerships and permissions right.

rsp · 11 February 2025 14:54

@Chabi02 we do not have that file in the logs/prod/ folder.

Maybe you did not set error reporting correctly in the php.ini or in the SuiteCRM under admin → system settings → Logger Settings

php.ini file error_reporting
Setting the following in php.ini would help get rid of these errors

error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE & ~E_WARNING

Set logger (admin → system settings → Logger Settings)

image1183×310 18.7 KB

and also do things mentioned by pgr

pgr · 11 February 2025 15:01

@rsp this is Symfony’s logging, it’s different from PHP logging and SuiteCRM logging… I know, this can be quite confusing…

This is configured as per @Farstar 's post above

rsp · 11 February 2025 16:41

Ohhhh now I understood it. Thank you for correction!

Chabi02 · 12 February 2025 15:08

Hi
I will make the test Friday evening when nobody work on the CRM and check if the issue still happen or not (to be able to fetch back a backup if necessary).

I’ll tell you…
Xavier

Chabi02 · 12 February 2025 15:09

By the way, I dont have the solution to my previous email as I dont find the information given by Farstar in my SuiteCRM 8.8 ?
Thanks again and again and again
Xavier

rsp · 12 February 2025 15:14

Maybe it is this code:

github.com

salesagility/SuiteCRM-Core/blob/hotfix/config/packages/monolog.yaml#L37


      
            #    type: firephp
            #    level: info
            #chromephp:
            #    type: chromephp
            #    level: info
          console:
            type: console
            process_psr_3_messages: false
            channels: [ "!event", "!doctrine", "!console", "!upgrade" ]
          
          deprecation:
            type: stream
            path: "%env(default:log.dir:env.logs:LOG_DIR)%/%env(default:log.deprecation.default:DEPRECATION_LOG_FILE_NAME)%"
            level: '%env(DEPRECATION_LOG_LEVEL)%'
            max_level: error
            channels: [ "deprecation" ]
          
          security:
            type: stream
            path: "%env(default:log.dir:env.logs:LOG_DIR)%/%env(default:log.security.default:SECURITY_LOG_FILE_NAME)%"
            level: '%env(SECURITY_LOG_LEVEL)%'

Or

github.com

salesagility/SuiteCRM-Core/blob/hotfix/config/packages/monolog.yaml#L88


      
            path: "%env(default:log.dir:env.logs:LOG_DIR)%/%env(default:log.main.default:MAIN_LOG_FILE_NAME)%"
            level: '%env(MAIN_LOG_LEVEL)%'
            channels: ["!event", "!upgrade", "!deprecation" , "!security"]
          console:
            type: console
            process_psr_3_messages: false
            level: warning
            action_level: info
            channels: ["!event", "!doctrine", "!upgrade", "!deprecation"]
          
          deprecation:
            type: stream
            path: "%env(default:log.dir:env.logs:LOG_DIR)%/%env(default:log.deprecation.default:DEPRECATION_LOG_FILE_NAME)%"
            level: '%env(DEPRECATION_LOG_LEVEL)%'
            max_level: error
            channels: [ "deprecation" ]
          
          security:
            type: stream
            path: "%env(default:log.dir:env.logs:LOG_DIR)%/%env(default:log.security.default:SECURITY_LOG_FILE_NAME)%"
            level: '%env(SECURITY_LOG_LEVEL)%'

Chabi02 · 14 February 2025 11:44

Thanks Rsp,
I have seen this code but as I was not 100% sure, and as I dont want to crash in any manner a production SuiteCRM, I did not change it before. I will make a try this evening when office is closed.

Thanks
Xavier

rsp · 14 February 2025 17:14

Sounds like a plan! All the best

Chabi02 · 15 February 2025 09:05

Hi everyone,
To keep you in touch, I come back to tell you the results.
This morning, I log by FTP to rename the prod.deprecations.log, purge the cache and check if all is running after that.

And then… before doing anything, I see the prod.deprecations.log file with a size of… 1 octet (byte) without doing anything !!

I dont know if the V8.8 have solved the issue or if the order
./bin/console cache:clear
done 2 days ago did something on this, but so far, I can see the file is empty. I can access to the dashboard, the admin page, the studio…

I dont have any explanation on this and how this has occured.

If somebody knows how this can occurs or if the V8.8 fix this, please tell me ! So far, it seems to be fixed (and I did not do anything else except the upgrade to the V8.8 and a cache purge in console).
To be sure, I have checked the size of the file yesterday on the JetBackup : 29.7Gb…
Incredible…

Have a nice day eveyone
Xavier

EDIT : I have also checked, I have no logrotate known on my side, but maybe there is one in SuiteCRM now ?

rsp · 16 February 2025 05:17

That’s good to know. Maybe it is fixed!

Chabi02 · 4 March 2025 15:19

Hi everyone,
Back for a follow-up.
Since the upgrade to V8.8, no more issue with this deprecation log.

So far, this issue seems to be fixed for good.
Have a nice day !
Xavier

rsp · 5 March 2025 01:04

That’s awesome!