Varzaru Razvan-Liviu added a comment - 2025-04-14 07:08 - edited danblack not sure if something server side caused this or it's the VM's , but: https://buildbot.mariadb.org/#/builders/695/builds/721/steps/5/logs/stdio ERROR 1045 ( 28000 ): Access denied for user 'buildbot' @ 'localhost' (using password: NO) + res= 1 This is where the failure comes from. faust on VM redeployment on Production, did you changed something about the buildbot user on VM's (sudo, password)? Is it assuming the default password set on VM's for buildbot user: mysql -ubuildbot -ptest -e 'SHOW GRANTS' which fails with the above error.

Daniel Black added a comment - 2025-04-14 22:36 Quite right - unix password on buildbot user seems likely cause. Failing that something logged in the mariadb.service journal or something system wide.

Daniel Black added a comment - 2 days ago Fixed in server - MDEV-36681 Also checked pam_v1 to see if chown/chmod still required. In short, yes it is as the unix_chkpwd is running as the mysql user (real), despite being suid (effective - geteuid) but sets the effective to mysql before attempting to access /etc/shadow. 1947 openat(AT_FDCWD, "/etc/passwd", O_RDONLY|O_CLOEXEC) = 3 1947 fstat(3, {st_mode=S_IFREG|0644, st_size=1521, ...}) = 0 1947 lseek(3, 0, SEEK_SET) = 0 1947 read(3, "root:x:0:0:root:/root:/bin/bash\nbin:x:1:1:bin:/bin:/sbin/nologin\ndaemon:x:2:2:daemon:/sbin:/sbin/no"..., 4096) = 1521 1947 close(3) = 0 1947 getuid() = 991 1947 setuid(991) = 0 1947 read(0, "notmypassword\0", 513) = 13 1947 openat(AT_FDCWD, "/etc/passwd", O_RDONLY|O_CLOEXEC) = 3 1947 fstat(3, {st_mode=S_IFREG|0644, st_size=1521, ...}) = 0 1947 lseek(3, 0, SEEK_SET) = 0 1947 read(3, "root:x:0:0:root:/root:/bin/bash\nbin:x:1:1:bin:/bin:/sbin/nologin\ndaemon:x:2:2:daemon:/sbin:/sbin/no"..., 4096) = 1521 1947 close(3) = 0 1947 openat(AT_FDCWD, "/etc/shadow", O_RDONLY|O_CLOEXEC) = -1 EACCES (Permission denied)