Boot and allocation of memory right in the middle of it fails

[rajeshXYZ]

Linux 5.15.98-0psh1 #0psh1 SMP PREEMPT Sat, 4 Mar 2023 01:01:29 +0000 x86_64 GNU/Linux

PRETTY_NAME="Debian GNU/Linux 9 (stretch)

System boots

Tue Nov 28 11:10:10 2023] Adding 8388604k swap on /swapfile. Priority:0 extents:220 across:17506300k SSFS [Tue Nov 28 11:10:10 2023] kal: generic_netlink_register ... [Tue Nov 28 11:10:10 2023] kal: generic netlink registered family 25 [Tue Nov 28 11:10:10 2023] serviceable_lsm: initialized shared cpp [Tue Nov 28 11:10:10 2023] serviceable_lsm: initializing proc userspace access ... [Tue Nov 28 11:10:10 2023] cskal_proc_create 0 mem ... [Tue Nov 28 11:10:10 2023] serviceable_lsm: initialized proc userspace access [Tue Nov 28 11:10:10 2023] serviceable_lsm: initialization complete [Tue Nov 28 11:10:10 2023] ServiceableModuleInit_Deferred: 0 [Tue Nov 28 11:10:10 2023] pinned_lsm[559]: load_serviceable_symbols... [Tue Nov 28 11:10:10 2023] fuse: init (API version 7.34) [Tue Nov 28 11:10:12 2023] pinned_lsm[559]: load_serviceable_symbols succeeded [Tue Nov 28 11:10:12 2023] pinned_lsm[559]: load_network_ops_symbols... [Tue Nov 28 11:10:12 2023] manual prevention is enabled [Tue Nov 28 11:10:12 2023] network telemetry is enabled [Tue Nov 28 11:10:12 2023] network event is enabled [Tue Nov 28 11:10:12 2023] script control is enabled [Tue Nov 28 11:10:12 2023] filesystem event is enabled [Tue Nov 28 11:10:12 2023] PacketFilterAttached network events enabled. [Tue Nov 28 11:10:12 2023] FS-Cache: Loaded [Tue Nov 28 11:10:12 2023] FS-Cache: Netfs 'nfs' registered for caching [Tue Nov 28 11:10:12 2023] NFS: Registering the id_resolver key type [Tue Nov 28 11:10:12 2023] Key type id_resolver registered

Meanwhile gluster tries to allocate RAM and fails while the system is still organising

`Meanwhile gluster was trying to allocate memory and failed.

023-11-28 11:09:04.472130 +0000] W [glusterfsd.c:1429:cleanup_and_exit] (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x74a4) [0x7fb68fc324a4] -->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xfd) [0x5576dee0b2ad] -->/usr/sbin/glusterfs(cleanup_and_exit+0x54) [0x5576dee0b104] ) 0-: received signum (15), shutting down
[2023-11-28 11:11:16.307775 +0000] I [MSGID: 100030] [glusterfsd.c:2683:main] 0-/usr/sbin/glusterfs: Started running version [{arg=/usr/sbin/glusterfs}, {version=9.6}, {cmdlinestr=/usr/sbin/glusterfs -s localhost --volfile-id gluster/nfs -p /var/run/gluster/nfs/nfs.pid -l /var/log/glusterfs/nfs.log -S /var/run/gluster/166e1f61ab775b82.socket}]
[2023-11-28 11:11:16.308454 +0000] I [glusterfsd.c:2418:daemonize] 0-glusterfs: Pid of current running process is 5440
[2023-11-28 11:11:16.310560 +0000] I [socket.c:928:__socket_server_bind] 0-socket.glusterfsd: closing (AF_UNIX) reuse check socket 9
[2023-11-28 11:11:16.311245 +0000] I [MSGID: 101190] [event-epoll.c:670:event_dispatch_epoll_worker] 0-epoll: Started thread with index [{index=0}]
[2023-11-28 11:11:16.311294 +0000] I [MSGID: 101190] [event-epoll.c:670:event_dispatch_epoll_worker] 0-epoll: Started thread with index [{index=1}]
[2023-11-28 11:11:16.512564 +0000] W [glusterfsd.c:1429:cleanup_and_exit] (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x74a4) [0x7f3fbc2414a4] -->/usr/sbin/glusterfs(glusterfs_sigwaite`

From

glusterfs/glusterfsd/src/glusterfsd.c

Line 269 in c2d1fa5

{"io-engine", ARGP_IO_ENGINE_KEY, "ENGINE", OPTION_ARG_OPTIONAL,

that line 1429 indicattes it failed to allocated memory.

case ARGP_IO_ENGINE_KEY:
cmd_args->io_engine = gf_strdup(arg);
if (cmd_args->io_engine == NULL) {
argp_failure(state, -1, 0,
"Failed to allocate memory for "
"io-engine");
}
break;

Is this normal or could this be improved?