- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello,
The error "aws-sqsd: Cannot load config file. No such file or directory: "/etc/aws-sqsd.d/default.yaml" - (AWS::EB::SQSD::FatalError)" was thrown because EB could not find the configuration file for the SQS queue and this file is updated based on your environment configuration.
A potential reason why the sqsd failed to start could be memory issue. Could you verify your instance type and try a deployment using a larger instance type such as t4g.xlarge. Could you also verify if an initial deployment on a fresh instance works vs a deployment on an instance that was already deployed to. An initial deployment may be successful contrary to a subsequent deployment because when a new instance is launched and used, complete memory capacity is available for the SQSD daemon.
I found some third party related issues 1 and 2 that may be of help.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 8 Monaten
- AWS OFFICIALAktualisiert vor 8 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
It wasn't a memory issue. It looks like CloudFormation isn't working with the current Solution Stack.
The process isn't starting since the default.yaml is missing, and it's missing because the command to get it isn't functional?
I ran it (
sudo /opt/elasticbeanstalk/bin/get-config --output YAML meta -k sqsdconfig
) manually on a lower environment for testing purposes and put the cleaned-up contents into the default.yaml and the service spun up no problem.Current CF runs says:
getMetadata.py --yaml --path AWS::ElasticBeanstalk::Ext._SqsDaemonConfigFileContent | sed -e "s/'//g" -e 's/"//g' > /etc/aws-sqsd.d/default.yaml