Project

General

Profile

Actions

Bug #30

closed

Redis server fails to start at boot time

Added by Emmanuel Jubera [SAFT] over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
10/26/2022
Due date:
% Done:

0%

Estimated time:
Hardware platform:
Solidrun (aarch64)
OS Affects Version/s:
arz-1.0, arz-1.0-update
OS Fix Version/s:
arz-1.0.1
Labels:

Description

When using Redpesk OS image generated on the 12th of October, one can notice that the redis service didn't start properly:

[root@localhost ~]# systemctl status redis
Warning: The unit file, source configuration file or drop-ins of redis.service changed on disk. Run 'systemctl daemon-reload' to reload units.
- redis.service - Redis persistent key-value database
   Loaded: loaded (/usr/lib/systemd/system/redis.service; enabled; vendor preset: disabled)

   Active: failed (Result: signal) since Fri 2018-06-22 13:13:20 CEST; 8min ago
  Process: 470 ExecStart=/usr/bin/redis-server /etc/redis.conf --supervised systemd (code=killed, signal=KILL)
  Process: 459 ExecStartPre=/bin/sh -c ([ ! -d /var/log/redis ] ||  chsmack -a System -r /var/log/redis) (code=exited, status=0/SUCCESS)
  Process: 435 ExecStartPre=/bin/sh -c ([ ! -d /var/lib/redis ] ||  chsmack -a System -r /var/lib/redis) (code=exited, status=0/SUCCESS)
 Main PID: 470 (code=killed, signal=KILL)

Jun 22 13:12:07 localhost systemd[1]: Starting Redis persistent key-value database...
Jun 22 13:12:08 localhost systemd[1]: Started Redis persistent key-value database.
Jun 22 13:13:20 localhost.localdomain systemd[1]: redis.service: Main process exited, code=killed, status=9/KILL
Jun 22 13:13:20 localhost.localdomain systemd[1]: redis.service: Failed with result 'signal'. 

When looking at the system journal it appears that redis server was killed (because using too much memory ?):

Jun 22 13:13:20 localhost.localdomain kernel: Out of memory: Killed process 470 (redis-server) total-vm:1088360kB, anon-rss:843668kB, file-rss:8kB, shmem-rss:0kB, UID:987 pgtables:1728kB oom_score_adj:0

Actions #1

Updated by José Bollo over 1 year ago

  • Status changed from New to In Progress
  • Assignee changed from Pierre Marzin to Emmanuel Jubera [SAFT]

The issue seems fixed in latest version.

To be validated and closed.

Actions #2

Updated by Emmanuel Jubera [SAFT] over 1 year ago

  • Status changed from In Progress to Resolved
  • OS Fix Version/s arz-1.0.0 added

Fixed with arz 1.0 generated on the 14th of November, 2022.

NAME="redpesk Linux"
VERSION="Arz 1.0 LTS"
VERSION_ID="1.0"
VERSION_CODENAME="arz"
ID="redpesk"
ID_LIKE="rhel fedora centos"
PLATFORM_ID="platform:rparz"
PRETTY_NAME="redpesk Linux Arz 1.0 LTS"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redpesk:centos:arz"
HOME_URL="https://redpesk.bzh/"
redpesk_MANTISBT_PROJECT="redpesk-arz"
redpesk_MANTISBT_PROJECT_VERSION="arz"
ARCH="aarch64"
BUILD_DATE="2022-11-14 13:09:51"
SECURITY_MODEL="smack"

Actions #3

Updated by Sebastien Douheret [IoT.bzh] over 1 year ago

  • Target version changed from arz-1.0-update to arz-1.0.1
Actions #4

Updated by Sebastien Douheret [IoT.bzh] over 1 year ago

  • OS Fix Version/s arz-1.0.1 added
  • OS Fix Version/s deleted (arz-1.0.0)
Actions #5

Updated by Sebastien Douheret [IoT.bzh] over 1 year ago

  • OS Affects Version/s arz-1.0, arz-1.0-update added
Actions #6

Updated by Sebastien Douheret [IoT.bzh] over 1 year ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF