What should you do if imanage and isetup does not work?

What should you do if imanage and isetup does not work?
0

indeni@indeni-1:~$ imanage

imanage: command not found

indeni@indeni-1:~$ imanage

imanage: command not found

indeni@indeni-1:~$ isetup

ruby: No such file or directory -- /usr/share/indeni-tools/setup.rb (LoadError)



Restarting server then allowed the tools to load. Any reason why?

imanage and isetup are bash aliases created for user indeni.


Both are helpful utilities.


isetup is a utility focused on the initial setup. It is where you set up your IP address, NTP server, timezone, DNS, etc. It is usually launched right after an initial install but it can be invoked just by typing isetup at the command prompt. In past versions you would need to sudo bash (get into root shell).


OS Configuration Wizard

This wizard will guide you through the setting of various network and system settings for this machine.

Do you want to proceed with the configuration wizard [y/n]?

Please select an option to proceed with:

  1. Configure apt-get proxy
  2. Configure network interface
  3. Configure NTP servers
  4. Change time zone
  5. Change hostname
  6. Quit

imanage is Indeni system focused. It allows you to perform basic server functions surrounding package updates and services.


indeni Packages Management


This wizard will guide you through common management operations related to indeni packages.

Please select an option to proceed with:

  1. Display installed indeni packages
  2. Upgrade all indeni packages
  3. Restart indeni services (collector and server)
  4. Change indeni source packages
  5. Quit



@paul do you have any wise offerings? :)

Hello Liz,
Did you install/re-install indeni-tools?
If not, how did you change to user "inden"?


The problem you're describing happened because your aliases were not loaded.

These messages are mostly related to switching the user without a login shell.

su - invokes a login shell after switching the user. A login shell resets most environment variables, providing a clean base.

su just switches the user, providing a normal shell with an environment nearly the same as with the old user.

This is why restarting the server solved your issue, because upon restarting you receive a shell login.

typing "sudo su - indeni" would have also do the job, and without restarting.


Here is a little demonstration of how to "lose" and re-acquire the imanage/isetup aliases.

indeni@indeni-server:~$ alias
alias alert="notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e "\""s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//"\"")""
alias egrep="egrep --color=auto"
alias fgrep="fgrep --color=auto"
alias grep="grep --color=auto"
alias imanage="ruby /usr/share/indeni-tools/manage/indeni-manage.rb"
alias isetup="ruby /usr/share/indeni-tools/setup/setup.rb user-request"
alias l="ls -CF"
alias la="ls -A"
alias ll="ls -alF"
alias ls="ls --color=auto"
indeni@indeni-server:~$ sudo su - 
root@indeni-server:~# sudo su indeni
indeni@indeni-server:/root$ alias
alias alert="notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e "\""s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//"\"")""
alias egrep="egrep --color=auto"
alias fgrep="fgrep --color=auto"
alias grep="grep --color=auto"
alias l="ls -CF"
alias la="ls -A"
alias ll="ls -alF"
alias ls="ls --color=auto"
indeni@indeni-server:/root$ sudo su - indeni

Installed indeni packages:

indeni-collector 5.9.3.471
indeni-server 5.9.3.471
indeni-tools 0.0.30.39
indeni@indeni-server:~$ alias
alias alert=“notify-send --urgency=low -i “$([ $? = 0 ] && echo terminal || echo error)” “$(history|tail -n1|sed -e “”“s/^\s*[0-9]+\s*//;s/[;&|]\s*alert$//”””)""
alias egrep="egrep --color=auto"
alias fgrep="fgrep --color=auto"
alias grep="grep --color=auto"
alias imanage="ruby /usr/share/indeni-tools/manage/indeni-manage.rb"
alias isetup="ruby /usr/share/indeni-tools/setup/setup.rb user-request"
alias l="ls -CF"
alias la="ls -A"
alias ll="ls -alF"
alias ls="ls --color=auto"
indeni@indeni-server:~$



If this still doesn’t make sense to you, please elaborate a little more on your steps prior to having this issue.

Reshef.