[MCOL-1467] rc-local service doesnt always start correctly on amazon ami centos7 Created: 2018-06-13  Updated: 2023-10-26  Resolved: 2018-06-27

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.1.5
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: David Hill (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

because of this error, columnstore doesnt startup on a node after its rebooted

still the same issue, rc-local isnt starting all the time.

some of the status after reboot

systemctl status rc-local.service
● rc-local.service - /etc/rc.d/rc.local Compatibility
Loaded: loaded (/etc/systemd/system/rc-local.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2018-06-13 18:07:02 UTC; 7min ago
Process: 869 ExecStart=/etc/rc.d/rc.local start (code=exited, status=203/EXEC)

systemctl status rc-local.service
● rc-local.service - /etc/rc.d/rc.local Compatibility
Loaded: loaded (/etc/systemd/system/rc-local.service; static; vendor preset: disabled)
Active: inactive (dead)strong text

 Comments   
Comment by David Hill (Inactive) [ 2018-06-26 ]

the ami instance has the rc.local executiable flags set at build time

but the new instances that get launched from the ami are getting changed for some reason and this is why the service isnt starting

ll rc.local
-rwxrwxrwt. 1 root root 1290 Jun 19 15:58 rc.local

to

[root@ip-172-31-42-74 ~]# ll /etc/rc.d/rc.local
rw-rw-rw 1 root root 1450 Jun 26 21:19 /etc/rc.d/rc.local

Comment by David Hill (Inactive) [ 2018-06-27 ]

ok, problem found to be in out code, in the module_installer.sh file. it was changing rc.local to 666.

fix with pull release and will release a 1.1.5-2 for AMI only.

https://github.com/mariadb-corporation/mariadb-columnstore-engine/pull/510

Comment by David Hill (Inactive) [ 2018-06-27 ]

https://github.com/mariadb-corporation/mariadb-columnstore-engine/pull/510

can you review for me.

Comment by Daniel Lee (Inactive) [ 2018-06-27 ]

Build tested: 1.1.5-1 (ami-a2763dda)
Failover and instance reboot worked fine, but when running installtest, it refused created instances refused connection.

Build verified: 1.1.5-1 release ami (ami-4987cc31)
Restarted both failover and installtest. both worked fine.

Generated at Thu Feb 08 02:28:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.