Moving to upstart from busybox causing the kernel panic - upstart

We created simple linux file system using the busybox and it is working succesfully.
But we tried to move from busybox init process to upstart init. But we are facing the kernel panic, when we are trying to do init=/sbin/init.upstart. What could be the reason?
The upstart file image is created by upstart 0.3.9 package.

Related

How do you run redis for jaseci is there a specific command to run

Is there a way that is jaseci specific to run redis in the terminal, because jaseci studio is complaining in the logs and the graphs is not working as expected because it requires redis.
I'm expecting redis to work on jsserv so that the graph can work properly.
You'd need to run the standard redis-server in a separate terminal before starting jsserv runserver.
Assuming you're using an Ubuntu (or Debian) distro, to install redis-server use sudo apt install redis-server

Jupyter notebook MATLAB kernel: Runs, but does not display output

The issue is as shown in the image below. The kernel runs but the output is not displayed.
For installation, I followed the steps under 'Python side configuration' and 'MATLAB side configuration' here.
Have tried the following:
All other kernels work normally
The issue persists in both Firefox and Chrome
Edit: There were no issues in the installation of the python engine.
sudo python3 setup.py install
[sudo] password for tinkidinki:
running install
running build
running build_py
running install_lib
copying build/lib/matlab/engine/_arch.txt -> /usr/local/lib/python3.8/dist-packages/matlab/engine
running install_egg_info
Removing /usr/local/lib/python3.8/dist-packages/matlabengineforpython-R2020b.egg-info
Writing /usr/local/lib/python3.8/dist-packages/matlabengineforpython-R2020b.egg-info
Most likely your antivirus program is blocking the output (e.g. Adaware antivirus often causes this problem).
If this is not the case: sometimes the output is shown in the command prompt window instead of in the Jupyter notebook, check if this is the case.
Try restarting the kernel in kernel option (yup, more of a workaround...)

How to uninstall eclipse che completely on mac osx?

How to uninstall eclipse che completely on mac osx?
Used mac osx installer to install binary. Seems che is always running on 8080 even killed the process and stopped docker.
https://eclipse.org/che/
I couldn't find the better way for uninstall on Mac but you can stop the Tomcat embedded in Eclipse Che.
The path is /Applications/EclipseChe3.12.5.2.app/Contents/Resources/eclipse-che/tomcat/bin
Next step is stop the Tomcat instance and finally delete the folder EclipseChe3.12.5.2.app because that's my Eclipse Che version.
So, I hope this is helpfully for you
If you are using Docker the process is different.
Get the list of active instance in Docker by running the following command in Terminal: docker ps
Then you can stop the running instance by running in docker stop XXX where XXX is the name of the running container instance. You may have more than one container instance to stop.
Then you can remove it by running docker rm XXX and then you can list images that are present on your system by running docker images
If you want to completely remove Che, then pickup for the images list the ones that are related to che and remove them by running the following command: docker mi image_name
Last command to stop docker on your mac will be docker-machin stop environment_name. If you do not know the name of the running environment you can figure it out by running docker-machine ls

Launcher service doesn't auto start on Ubuntu 14.04

For Linux installer, we have added a custom launcher for auto start of service (see pic below).
We are using install4j v5.1.6. It creates a link in /etc/init.d/myService.sh which points to the /bin/myService.sh .
It works properly in Ubuntu 13. On system restart, service auto starts properly.
On Ubuntu 14 this doesn't work. Service starts first time after installation. But on system restart, service doesn't auto start.
On further investigation, running these commands on Ubuntu 14 enabled auto start.
after installation
cd /etc/init.d
sudo update-rc.d myService.sh defaults
Under installer, install a service, auto start is set to true.
Is this a limitation of install4j that it doesn't register with update-rc.d ?
Do we know on which Linux systems copying to /etc/init.d/ is sufficient ?
Our script is similar to : www.shayanderson.com/linux/add-startup-script-or-service-with-linux-on-bootup.htm . What we don't have is update-rc.d and chkconfig. And install4j does the task of copying it to /etc/init.d/
Thanks !
http://s27.postimg.org/o5bih55kz/Launcher_Configuration.png
http://s3.postimg.org/icitxy96b/Launcher_Setup.png
As of 5.1.x, install4j does not integrate services into runlevels, it only creates the symlink to the start script in /etc/init.d.
Integrating it into runlevels has to be done manually, such as by calling update-rc.d or whatever other tool the particular distribution provides.

Can Upstart be installed side-by-side with other init script?

Can upstart be installed along side other init system? Upstart is quite handy in creating a daemon script written in PHP as it can respawn process. Unfortunately, it will be replace with systemd in the next ubuntu release. And how about other Linux distro? Centos, RedHat.
Yes, Upstart can be installed alongside system V init scripts. But, I would recommend using other process monitoring tools like "monit" over upstart because of the following reasons:
a. upstart scripts are too low level.
b. All debian systems(includes ubuntu) will be moving away from upstart back to systemd. Reference here.