v2.5.0 crypt library requires GLIBC_2.25
TLDR: hang, restart, hang, restart...
I'm running a small Pleroma instance on an 1C1G tiny VPS and everything works fine. The memory consumed by the Pleroma process fluctuates roughly around 160-240MB.
But today when I update to v2.5.0, it can't be started again. Here are some sample logs:
Dec 24 12:08:51 constance systemd[1]: Started Pleroma social network.
Dec 24 12:08:56 constance pleroma[1647]: 2022-12-24 12:08:56.440861 supervisor_report #{label=>{supervisor,start_error},report=>[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,{on_load_function_failed,crypt}},{offender,[{pid,undefined},{id,kernel_safe_sup},{mfargs,{supervisor,start_link,[{local,kernel_safe_sup},kernel,safe]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
Dec 24 12:08:56 constance pleroma[1647]: 2022-12-24 12:08:56.440951 crash_report #{label=>{proc_lib,crash},report=>[[{initial_call,{supervisor,kernel,['Argument__1']}},{pid,<0.3543.0>},{registered_name,[]},{error_info,{exit,{on_load_function_failed,crypt},[{init,run_on_load_handlers,0,[]},{kernel,init,1,[{file,"kernel.erl"},{line,189}]},{supervisor,init,1,[{file,"supervisor.erl"},{line,301}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,417}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,385}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,226}]}]}},{ancestors,[kernel_sup,<0.3516.0>]},{message_queue_len,0},{messages,[]},{links,[<0.3518.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,610},{stack_size,28},{reductions,262}],[]]}
Dec 24 12:08:57 constance pleroma[1647]: 2022-12-24 12:08:57.458325 crash_report #{label=>{proc_lib,crash},report=>[[{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{pid,<0.3515.0>},{registered_name,[]},{error_info,{exit,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,138}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,226}]}]}},{ancestors,[<0.3514.0>]},{message_queue_len,1},{messages,[{'EXIT',<0.3516.0>,normal}]},{links,[<0.3514.0>,<0.3513.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,376},{stack_size,28},{reductions,190}],[]]}
Dec 24 12:08:57 constance pleroma[1647]: 2022-12-24 12:08:57.468156 std_info #{label=>{application_controller,exit},report=>[{application,kernel},{exited,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}}},{type,permanent}]}
Dec 24 12:08:57 constance pleroma[1647]: {"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}}}"}
Dec 24 12:08:57 constance pleroma[1647]: Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}}})
Dec 24 12:08:57 constance pleroma[1647]: #015
Dec 24 12:08:58 constance pleroma[1647]: Crash dump is being written to: erl_crash.dump...done
Dec 24 12:08:58 constance systemd[1]: pleroma.service: Main process exited, code=exited, status=1/FAILURE
Dec 24 12:08:58 constance pleroma[1697]: --rpc-eval : RPC failed with reason :nodedown
Dec 24 12:08:58 constance systemd[1]: pleroma.service: Control process exited, code=exited status=1
Dec 24 12:08:58 constance systemd[1]: pleroma.service: Unit entered failed state.
Dec 24 12:08:58 constance systemd[1]: pleroma.service: Failed with result 'exit-code'.
Dec 24 12:08:58 constance systemd[1]: pleroma.service: Service hold-off time over, scheduling restart.
Dec 24 12:08:58 constance systemd[1]: Stopped Pleroma social network.
Dec 24 12:08:58 constance systemd[1]: Started Pleroma social network.
...
Since it was killed at start time, I guess the culprit might be the new version of Elixir.
Now I'm trying to roll back to v2.4.5. Fortunately, a database backup was made before the upgrade.
Edited by debula