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

Runtime Error: Invalid Memory Address or Nil Pointer Dereference during Fresh Install #1089

Closed
kavibritto opened this issue Oct 13, 2023 · 4 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@kavibritto
Copy link

Describe the bug
After performing a fresh installation of Komiser, the application fails to start, and a runtime error occurs. The error message states: "runtime error: invalid memory address or nil pointer dereference." This error is preventing the application from functioning as expected.

To Reproduce
Steps to reproduce the behavior:

  1. Perform a fresh installation of Komiser on the target system.
  2. Attempt to start the Komiser application. ./komiser_Linux_x86_64 start --config config.toml --verbose
  3. Observe the runtime error: "invalid memory address or nil pointer dereference."
/komiser-latest # ./komiser_Linux_x86_64 start --config config.toml --verbose
INIT!!!
INFO[2023-10-13T07:27:08Z] Debug logging is enabled                     
INFO[2023-10-13T07:27:08Z] Data will be stored in SQLite                
INFO[2023-10-13T07:27:08Z] migrated to group #1 (20230413100000, 20230602100000, 20230619100000, 20231014100000) 
INFO[2023-10-13T07:27:08Z] Komiser version: 3.1.1, commit: 5fb674f0211958fd511b42cbec94dbaae1a41acd, buildt: 1696429830 
INFO[2023-10-13T07:27:08Z] Fetching resources workflow has started      
ERRO[2023-10-13T07:27:15Z] error fetching AWS resources                  err="runtime error: invalid memory address or nil pointer dereference"

Desktop (please complete the following information):

  • OS: Ubuntu 22.04 LTS
  • Version : Komiser 3.1.1
@kavibritto kavibritto added the bug Something isn't working label Oct 13, 2023
@github-actions
Copy link

Hey, thank you for opening your first Issue! 🙂 While a Tailwarden team member takes a look at your issue we would like to invite you to join our official Discord server, where you can interact directly with other contributors and Tailwarden team members. Link here: https://discord.tailwarden.com

@Azanul
Copy link
Collaborator

Azanul commented Oct 16, 2023

Screenshot 2023-10-16 at 2 10 30 PM

@Azanul
Copy link
Collaborator

Azanul commented Oct 16, 2023

[azan@azarch ~]$ ./komiser_Linux_x86_64 start --config config.toml --verbose
INIT!!!
INFO[2023-10-16T15:36:37+05:30] Debug logging is enabled                     
INFO[2023-10-16T15:36:37+05:30] Data will be stored in SQLite                
WARN[2023-10-16T15:36:37+05:30] AWS account cannot be inserted to database   
INFO[2023-10-16T15:36:37+05:30] there are no new migrations to run (database is up to date) 
INFO[2023-10-16T15:36:37+05:30] Komiser version: 3.1.1, commit: 5fb674f0211958fd511b42cbec94dbaae1a41acd, buildt: 1696429830 
INFO[2023-10-16T15:36:37+05:30] Fetching resources workflow has started      
WARN[2023-10-16T15:36:42+05:30] Failed to check for new version: Get "https://api.github.com/repos/tailwarden/komiser/releases/latest": context deadline exceeded (Client.Timeout exceeded while awaiting headers) 
INFO[2023-10-16T15:36:45+05:30] Fetched resources                             account=Test provider=AWS region=us-east-1 resources=0 service=EC2
INFO[2023-10-16T15:36:53+05:30] Fetched resources                             account=Test provider=AWS region=us-east-1 resources=0 service="Elastic IP"
INFO[2023-10-16T15:37:13+05:30] Fetched resources                             account=Test provider=AWS region=us-east-1 resources=1 service=Lambda
INFO[2023-10-16T15:37:21+05:30] Fetched resources                             account=Test provider=AWS region=us-east-1 resources=2 service=ACL
INFO[2023-10-16T15:37:22+05:30] Fetched resources                             account=Test provider=AWS region=us-east-1 resources=8 service=Subnet
[azan@azarch ~]$ cat /etc/os-release
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

@kavibritto
Copy link
Author

@Azanul
need nil check for instance key pair name. because we are using ec2 instance with Ec2 session managers. in this case we don't have an ec2 key pair for the instance.

please refer to the screenshot.
komiser-keypair issue

kavibritto pushed a commit to kavibritto/komiser that referenced this issue Oct 16, 2023
mlabouardy added a commit that referenced this issue Oct 16, 2023
 #1089 Added nil check on associated KeyPair
@mlabouardy mlabouardy assigned kavibritto and unassigned mlabouardy Oct 16, 2023
@mlabouardy mlabouardy added this to the v3.1.2 milestone Oct 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants