Gitlab runner doesn't start on Apple M1 - gitlab

On my instance,
I added a runner on a Apple Silicon M1, but this runner doesn't start.
That's why I assigned a project to it, with the hope of starting, but I see this
But how can I check why is there a red ! ?
What prevents to start it ?
This is what I did.
Create docker runner:
docker stop gitlab-runner && docker rm gitlab-runner
docker run -d --name gitlab-runner --restart always \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /Users/Shared/gitlab-runner/config:/etc/gitlab-runner \
gitlab/gitlab-runner:latest
register runner:
docker run --rm -v /Users/Shared/gitlab-runner/config:/etc/gitlab-runner gitlab/gitlab-runner register \
--non-interactive \
--executor "docker" \
--docker-image hannesa2/android-ndk:api28_emu \
--url "http://latitude:8083/" \
--registration-token "<TOKEN>" \
--description "M1 pro Android NDK + Emu" \
--tag-list "android,android-ndk,android-emu" \
--run-untagged="true" \
--locked="false" \
--access-level="not_protected"
and I see this in docker log
Runtime platform arch=arm64 os=linux pid=8 revision=4b9e985a version=14.4.0
Starting multi-runner from /etc/gitlab-runner/config.toml... builds=0
Running in system-mode.
Configuration loaded builds=0
listen_address not defined, metrics & debug endpoints disabled builds=0
[session_server].listen_address not defined, session endpoints disabled builds=0
ERROR: Checking for jobs... forbidden runner=Jc2yrs_v
ERROR: Checking for jobs... forbidden runner=Jc2yrs_v
ERROR: Checking for jobs... forbidden runner=Jc2yrs_v
ERROR: Runner http://latitude:8083/Jc2yrs_v8JkJyMJAGUd_ is not healthy and will be disabled!
Configuration loaded builds=0
Thank you

Related

Getting error while running to "runqemu qemux86-64"

I want to run the graphic image of qemux86-64 which I have built with yocto. When I am running command "runqemu qemux86-64" or "runqemu" or "runqemu core-image-minimal" I am getting the following error.
nikita#ubuntu:~/yocto/poky/build$ runqemu qemux86-64
runqemu - INFO - Running MACHINE=qemux86-64 bitbake -e ...
runqemu - INFO - Continuing with the following parameters:
KERNEL: [/home/nikita/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage--5.4.205+gitAUTOINC+aaaf9f090d_8a59dfded8-r0-qemux86-64-20220803111012.bin]
MACHINE: [qemux86-64]
FSTYPE: [ext4]
ROOTFS: [/home/nikita/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20220803111012.rootfs.ext4]
CONFFILE: [/home/nikita/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20220803111012.qemuboot.conf]
runqemu - INFO - Setting up tap interface under sudo
[sudo] password for nikita:
runqemu - INFO - Network configuration: ip=192.168.7.2::192.168.7.1:255.255.255.0
runqemu - INFO - Running /home/nikita/yocto/poky/build/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -drive file=/home/nikita/yocto/poky/build/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20220803111012.rootfs.ext4,if=virtio,format=raw -show-cursor -usb -device usb-tablet -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -cpu core2duo -m 256 -serial mon:vc -serial null -kernel /home/nikita/yocto/poky/build/tmp/deploy/images/qemux86-64/bzImage--5.4.205+gitAUTOINC+aaaf9f090d_8a59dfded8-r0-qemux86-64-20220803111012.bin -append 'root=/dev/vda rw mem=256M ip=192.168.7.2::192.168.7.1:255.255.255.0 oprofile.timer=1 '
runqemu - ERROR - Failed to run qemu: Could not initialize SDL(x11 not available) - exiting
runqemu - INFO - Cleaning up
Set 'tap0' nonpersistent
Only solution I found on internet that i should run nographic image for this which has worked fine for me but my requirement is graphic image for this. Help me to find the solution to run graphic image for this.
Your replies would be appreciated .
I was facing same issue recently and got fixed by below step,
Change
PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
to
PACKAGECONFIG_append_pn-qemu-system-native = " gtk+"
in conf/local.conf
Now recompile and start runqemu

Slurmd crashes when emulating a larger cluster in versions 21 and 22

I have been maintaining a Slurm simulator for ages. I have everything automated in other to try new features and keep my configuration up to date, version after version.
Unfortunately, from version 21, the front-end mode makes the slurmd daemon crash with the following error message:
slurmd: error: _find_node_record: lookup failure for node "slurm-simulator"
slurmd: error: _find_node_record: lookup failure for node "slurm-simulator", alias "slurm-simulator"
slurmd: error: slurmd initialization failed
The exact same container, with the same configuration but using version 20.11.9, works just fine. I reproduced the same steps manually in a VM to remove the noise introduced by the container, but the result is the same.
The attached configuration is available in the container.
[root#slurm-simulator /]# cat /etc/slurm/slurm.conf
ClusterName=simulator
SlurmctldHost=slurm-simulator
FrontendName=slurm-simulator
MpiDefault=none
ProctrackType=proctrack/linuxproc
ReturnToService=1
SlurmctldPidFile=/var/run/slurmctld.pid
SlurmctldPort=6817
SlurmdPidFile=/var/run/slurmd.pid
SlurmdPort=6818
SlurmdSpoolDir=/var/spool/slurmd
SlurmUser=root
StateSaveLocation=/var/spool/slurmctld
SwitchType=switch/none
TaskPlugin=task/none
InactiveLimit=0
KillWait=30
MinJobAge=300
SlurmctldTimeout=120
SlurmdTimeout=300
Waittime=0
SchedulerType=sched/backfill
SelectType=select/cons_tres
SelectTypeParameters=CR_Core
AccountingStorageType=accounting_storage/slurmdbd
JobCompType=jobcomp/none
JobAcctGatherFrequency=30
JobAcctGatherType=jobacct_gather/none
SlurmctldDebug=info
SlurmctldLogFile=/var/log/slurmctld.log
SlurmdDebug=info
SlurmdLogFile=/var/log/slurmd.log
SlurmdParameters=config_overrides
include /etc/slurm/nodes.conf
include /etc/slurm/partitions.conf
[root#slurm-simulator /]# cat /etc/slurm/nodes.conf
NodeName=node[001-10] RealMemory=248000 Sockets=2 CoresPerSocket=32 ThreadsPerCore=1 State=UNKNOWN NodeAddr=slurm-simulator NodeHostName=slurm-simulator
[root#slurm-simulator /]# cat /etc/slurm/partitions.conf
PartitionName=long Nodes=node[001-10] Default=YES State=UP OverSubscribe=NO MaxTime=14-00:00:00
The error can be reproduced by running the following commands:
docker run --rm --detach \
--name "${USER}_simulator" \
-h "slurm-simulator" \
--security-opt seccomp:unconfined \
--privileged -e container=docker \
-v /run -v /sys/fs/cgroup:/sys/fs/cgroup \
--cgroupns=host \
hpcnow/slurm_simulator:21.08.8-2 /usr/sbin/init
docker exec -ti ${USER}_simulator /bin/bash
slurmd -D -vvvvv
If you try the same command with v20.11.9 it will work. I have tried using the new SlurmdParameters=config_overrides option, but I still get the same problem.
Any ideas or suggestions?
Thanks!

Velero installation issue with AKS - "Error getting a backup store"

I am installing Velero in AKS.
Steps-
Velero(version 1.6.1) downloaded and unzipped it then moved it to the /usr/local/bin/
I have created Service Principle with the contributor role.
my credential-velero file-
AZURE_SUBSCRIPTION_ID=xxxxx-xxxxx-xxxxxxx-xxxxx
AZURE_TENANT_ID=xxxx-xxxxx-xxxxx-xxxxx-xxx
AZURE_CLIENT_ID=xxxx-xxxxxxx-xxxxx-xxxxx-xx
AZURE_CLIENT_SECRET=xxxx-xxxxx-xxxxx-xxxxx
AZURE_RESOURCE_GROUP=MC....
AZURE_CLOUD_NAME=AzurePublicCloud
Command I am using to install velero -
velero install \
--provider azure \
--plugins velero/velero-plugin-for-microsoft-azure:v1.2.0 \
--bucket velero \
--secret-file ./credentials-velero \
--backup-location-config resourceGroup=<RG name>,storageAccount=<storage acc name>[,subscriptionId=<subscription id>] \
--snapshot-location-config apiTimeout=5m[,resourceGroup=<RG name>,subscriptionId=<subscription id>]
Note- my RG is same for the AKS cluster and the backup storage account.
Error-
Phase for backup location is showing 'unknown'-
Logs of deployment -
time="2021-07-15T15:59:56Z" level=error msg="Error getting backup
store for this location" backupLocation=default controller=backup-sync
error="rpc error: code = Unknown desc =
azure.BearerAuthorizer#WithAuthorization: Failed to refresh the Token
for request to https://ma
nagement.azure.com/subscriptions/xxxx-xxxxxx-xxxxx-xxxxx%5D/resourceGroups/myRG/providers/Microso
ft.Storage/storageAccounts/storagename%5B/listKeys?%24expand=kerb&api-version=2019-06-01:
StatusCode=401 -- Original Error: adal: Refre sh request failed.
Status Code = '401'. Response body:
{"error":"invalid_client","error_description":"AADSTS1080615:
Invalid clie nt secret is provided.\r\nTrace ID:
xxxx-xxxx-xxxxx-xxxxx\r\nCorrelation ID: xxxx-xxxx-xxxxxx-xxxx\r
\nTimestamp: 2021-07-15
15:59:56Z","error_codes":[7000215],"timestamp":"2021-07-15
15:59:56Z","trace_id":"xxxx-xxxx-xxxxx-xxxx
","correlation_id":"xxx-xxxx-xxxx-xxxx-xxx","error_uri":"https://login.microsoftonline.com/error?c
ode=7000215"}"
error.file="/go/src/velero-plugin-for-microsoft-azure/velero-plugin-for-microsoft-azure/object_store.go:217"
error.funct ion=main.getStorageAccountKey
logSource="pkg/controller/backup_sync_controller.go:175"
Can anyone help me to understand what I am missing in setup.

I'm Getting this error while replacing the colors.xml file

Android resource compilation failed
Output: ------\app\src\main\res\mipmap-anydpi-v26\ic_launcher_round.xml:1: error: syntax error.
Command: -------\.gradle\caches\transforms-1\files-1.1\aapt2-3.2.1-4818971-windows.jar\e8f3f35941cfd68ed95c8ffe5df71903\aapt2-3.2.1-4818971-windows\aapt2.exe compile --legacy \
-o \
-----
project\SocialIntegration\app\build\intermediates\res\merged\debug \
----\SocialIntegration\app\src\main\res\mipmap-anydpi-v26\ic_launcher_round.xml
Daemon: AAPT2 aapt2-3.2.1-4818971-windows Daemon #0

wildfly-10 java.security.AccessControlException: access denied ("java.util.PropertyPermission" "module.path" "write")

I have a wildFly-10 that I built with flag -Dsecurity.manager=yes
I have a WAR deployed to wfly.
From the command-line I am executing this cmd
/usr/java/jdk1.8.0_72/jre/bin/java \
-Dsecmgr=true -Djava.security.manager \
-Djavax.xml.ws.spi.Provider=org.jboss.wsf.stack.cxf.client.ProviderImpl \
-Dlog4j.output.dir=/home/rsearls/j1/jbws/jbossws-cxf/modules/testsuite/cxf-tests/target \
-Dorg.jboss.ws.cxf.jaxws-client.bus.strategy=NEW_BUS \
-jar /home/rsearls/j1/wfly10/wildfly/build/target/wildfly-10.0.0.Final/jboss-modules.jar \
-mp /home/rsearls/j1/wfly10/wildfly/build/target/wildfly-10.0.0.Final/modules \
-jar /home/rsearls/j1/jbws/jbossws-cxf/modules/testsuite/cxf-tests/target/test-libs/jaxws-cxf-jbws3713-client.jar \
http://127.0.0.1:8080/jaxws-cxf-jbws3713//HelloService?wsdl 4 5
I am getting this exception.
Exception in thread "main" java.security.AccessControlException: access denied ("java.util.PropertyPermission" "module.path" "write")
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
at java.security.AccessController.checkPermission(AccessController.java:884)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at java.lang.System.setProperty(System.java:792)
at org.jboss.modules.Main.main(Main.java:152)
I've tried add a ref to a policy file like this,
-Djava.security.policy=/tmp/yy/server.policy \
The causes the run exception to be
An existing security manager was detected. You must use the -secmgr switch to start with a security manager.
I've tried various forms of secmgr
-secmgr
-Dsecmgr
-D-secmgr
but same exception
How can I resolve this?
Option "java.security.manager" is no longer supported use "-secmgr" instead. And must place -secmgr after the jboss-modules.jar reference.

Resources