Questions[ubuntu]

It's bringing me down the road of bitterness...When trying to install Git I get the following error that I don't know how to solve. Any suggestion is welcome. Thank you!

marlena@marlena-K55VD:~$ sudo apt-get install git
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias       
Leyendo la información de estado... Hecho
Se instalarán los siguientes paquetes adicionales:
  git-man liberror-perl
Paquetes sugeridos:
  git-daemon-run | git-daemon-sysvinit git-doc git-el git-email git-gui gitk
  gitweb git-cvs git-mediawiki git-svn
Se instalarán los siguientes paquetes NUEVOS:
  git git-man liberror-perl
0 actualizados, 3 nuevos se instalarán, 0 para eliminar y 4 no actualizados.
Se necesita descargar 22,8 kB/4.733 kB de archivos.
Se utilizarán 33,9 MB de espacio de disco adicional después de esta operación.
¿Desea continuar? [S/n] S
Ign:1 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 liberror-perl all 0.17025-1
Err:1 http://es.archive.ubuntu.com/ubuntu bionic/main amd64 liberror-perl all 0.17025-1
  409  Conflict [IP: 104.19.139.75 80]
E: Fallo al obtener http://es.archive.ubuntu.com/ubuntu/pool/main/libe/liberror-perl/liberror-perl_0.17025-1_all.deb  409  Conflict [IP: 104.19.139.75 80]
E: No se pudieron obtener algunos archivos, ¿quizás deba ejecutar «apt-get update» o deba intentarlo de nuevo con --fix-missing?

I have been trying to get interconnection between host and guest for a while [ubuntu18.04 - kvm qemu] because I am preconfiguring a webserver and I want to use the guest as a test bed. Overall, I can't go much further because the guest does have access to the host but not the other way around.

Searching I have read that I must create a bridge, and to do so modify /etc/networ/interfaces as follows (This is how I left it):

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
#a partir de aqui esta lo nuevo
auto br0
iface br0 inet static
address 192.168.1.37
network 192.168.1.0
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.1
bridge_ports enp4s0
bridge_stp off
bridge_fd 0
bridge_maxwait 0

of course in all the tutorials they mention eth0, however in ubuntu it does not exist and instead it is enp4s0.

Interestingly, after restarting the network service

/etc/init.d/network-manager restart

when checking the changes with ifconfig -a... no change appears and it looks like this.

enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 192.168.1.37  netmask 255.255.255.0  broadcast 192.168.1.255
    inet6 fe80::dd0b:4362:2668:e119  prefixlen 64  scopeid 0x20<link>
    ether da:01:3a:03:c0:67  txqueuelen 1000  (Ethernet)
    RX packets 365643  bytes 484283142 (484.2 MB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 177556  bytes 16509811 (16.5 MB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
    inet 127.0.0.1  netmask 255.0.0.0
    inet6 ::1  prefixlen 128  scopeid 0x10<host>
    loop  txqueuelen 1000  (Bucle local)
    RX packets 2566  bytes 247445 (247.4 KB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 2566  bytes 247445 (247.4 KB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
    inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
    ether 52:54:00:7f:cc:c1  txqueuelen 1000  (Ethernet)
    RX packets 83  bytes 5750 (5.7 KB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 57  bytes 5832 (5.8 KB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500
    ether 52:54:00:7f:cc:c1  txqueuelen 1000  (Ethernet)
    RX packets 0  bytes 0 (0.0 B)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 0  bytes 0 (0.0 B)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp4s0 was supposed to lose its IP and br0 shows up with my host's IP, but br0 doesn't show up. If I open virt-manager, in the network section of each machine it recognizes a new br0 bridge mode over enp4s0, however when the machine starts it tells me that the br0 device does not exist.

It's been a week and I'm getting too frustrated, I can't find any tutorial on the subject (mentioning ubuntu 18.04) even if I know that eth0 doesn't exist in ubuntu. And the few who perhaps mention it, following in its footsteps, doesn't matter, because br0 never gets created. I will be very grateful if you can tell me where I am missing.

PS: I have the bridge-utils package installed and updated

I have been looking for the best way to make a cloud server with Ubuntu when it restarts, or if it crashes for any reason and then gets up again, the nodeJs server that I have running on it automatically resumes.

To keep node running I do it with Forever, and to do what I'm asking about, I've found two ways:

1. Crontab:

Using Crontab as follows:

$ crontab -u myuser -e

and in the editor that opens by adding the following line

@reboot /usr/local/bin/forever start /your/path/to/your/app.js

2. Adding file to $ cd /etc/init.d

Add file and change permissions as follows:

$ cd /etc/init.d
$ sudo nano nodeapps

in the editor where nodeapp is created we put the following line:

sudo forever start /ruta/al/script/principal/de/la/app.js

We give execution permissions:

$ sudo chmod +x nodeapps

and add the script to boot:

$ sudo update-rc.d nodeapps defaults

Well, my question is which of these ways would be more stable, or if you have any other better way to do it?

I need to launch a docker-compose on an ubuntu-server every time it is rebooted.

I have tried to create a crontab like this:

@reboot docker-compose -f /home/user/docker-compose/docker-compose.yml up -d

But when I restart it this has not given results, any ideas?

I am trying to install a module nodejson an Amazon EC2 instance when I run ppm install markdown-pdfI get the following error:

> [email protected] install /home/ubuntu/fermat-org/api-server/node_modules/markdown-pdf/node_modules/phantomjs
> node install.js

PhantomJS not found on PATH
Download already available at /home/ubuntu/tmp/phantomjs/phantomjs-1.9.8-linux-x86_64.tar.bz2
FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory
Aborted (core dumped)
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! weird error 134
npm ERR! not ok code 0

I have node v0.12.25andnpm 1.3.10