Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 [Free Games Claimer] Unable to start addon #1617

Closed
Tonks140 opened this issue Oct 26, 2024 · 10 comments
Closed

🐛 [Free Games Claimer] Unable to start addon #1617

Tonks140 opened this issue Oct 26, 2024 · 10 comments
Labels
bug Something isn't working stale Element will be closed automatically

Comments

@Tonks140
Copy link

Description

Getting the error Error : /etc/cont-init.d/99-run.sh exiting 1 on starting. Config appears to be read correctly (I have redacted information from the config section of log).
This file does not appear to be present: /config/addons_autoscripts/free-games-claimer.sh

Reproduction steps

1. Set config file.
2. Start addon

Addon Logs

Starting...
/etc/cont-init.d/00-banner.sh: executing
-----------------------------------------------------------

 Add-on: Free Games Claimer (NoVNC not working)
 automatically claims free games on the Epic Games Store, Amazon Prime Gaming and GOG
-----------------------------------------------------------
 Add-on version: 1.6
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.2  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.10.3
 Home Assistant Supervisor: 2024.10.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
-----------------------------------------------------------
 Provided by: https://github.com/alexbelgium/hassio-addons 
-----------------------------------------------------------
/etc/cont-init.d/00-global_var.sh: executing
CMD_ARGUMENTS='node epic-games ; node prime-gaming ; node gog'
CONFIG_LOCATION='/config/addons_config/free_games_claimer/config.env'
Timezone set from Etc/UTC to Europe/London
/etc/cont-init.d/01-config_yaml.sh: executing
Setting permissions for the config.yaml directory

Load environment variables from /config/addons_config/free_games_claimer/config.env/config.yaml if existing

If accessing the file with filebrowser it should be mapped to /homeassistant/addons_config/free-games-claimer/config.yaml
---------------------------------------------------------
Wiki here on how to use : github.com/alexbelgium/hassio-addons/wiki/Add‐ons-feature-:-add-env-variables
SHOW='1'
WIDTH='1280'
HEIGHT='1280'
NOTIFY_TITLE='Free Games Claimer'
TIMEOUT='60'
LOGIN_TIMEOUT='180'
EMAIL=''
EG_PASSWORD=''
EG_OTPKEY=''
PG_PASSWORD=''
PG_OTPKEY=''
PG_REDEEM='1'
PG_CLAIMDLC='1'
GOG_EMAIL=''
GOG_PASSWORD=''
GOG_NEWSLETTER=''
LG_EMAIL=''
/etc/cont-init.d/01-custom_script.sh: executing
Execute /config/addons_autoscripts/free-games-claimer.sh if existing
---------------------------------------------------------
If accessing the file with filebrowser it should be mapped to /config/addons_autoscripts/free-games-claimer.sh
Wiki here : github.com/alexbelgium/hassio-addons/wiki/Add-ons-feature-:-customisation
... no script found, exiting
/etc/cont-init.d/20-folders.sh: executing
Creating config location ...
Copying files if needed...
/etc/cont-init.d/99-run.sh: executing
[10:05:32] WARNING: A default config.env file was copied in /config/addons_config/free_games_claimer. Please customize according to https://github.com/vogler/free-games-claimer/tree/main#configuration--options and restart the add-on
cp: -r not specified; omitting directory '/config/addons_config/free_games_claimer/config.env'
Error : /etc/cont-init.d/99-run.sh exiting 1

Architecture

aarch64

OS

HAos

@Tonks140 Tonks140 added the bug Something isn't working label Oct 26, 2024
Copy link
Contributor

github-actions bot commented Nov 3, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Element will be closed automatically label Nov 3, 2024
@robvangeloven
Copy link

Just adding that I have the same issue so this doesn't get closed automatically

@github-actions github-actions bot removed the stale Element will be closed automatically label Nov 10, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Element will be closed automatically label Nov 17, 2024
@Tonks140
Copy link
Author

Does anyone have any ideas on how to get this working?

@github-actions github-actions bot removed the stale Element will be closed automatically label Nov 24, 2024
@robvangeloven
Copy link

Does anyone have any ideas on how to get this working?

No idea. If I could fine the script in question in the repo I might have a starting point in figuring out how to fix this but it doesn't show up when I search for it.

Copy link
Contributor

github-actions bot commented Dec 1, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Element will be closed automatically label Dec 1, 2024
@FeikoJoosten
Copy link

[10:05:32] WARNING: A default config.env file was copied in /config/addons_config/free_games_claimer. Please customize according to https://github.com/vogler/free-games-claimer/tree/main#configuration--options and restart the add-on

The log states what you need to do. Make sure you've customized your config.env.

The mentioned script /config/addons_autoscripts/free-games-claimer.sh is only relevant if you want to run custom code. Which isn't relevant for most users.

@alexbelgium
Copy link
Owner

Is it better in the latest pushed version ?
There was an error in the handling of config.env that should have been solved through #1655

@alexbelgium
Copy link
Owner

ah no it's another error in config.yaml script - I'll solve it a bit later

@github-actions github-actions bot removed the stale Element will be closed automatically label Dec 8, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Element will be closed automatically label Dec 15, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale Element will be closed automatically
Projects
None yet
Development

No branches or pull requests

4 participants