apache2 refusing to start

When i try to start apache2 this error message returns

See "systemctl status apache2.service" and "journalctl -xe" for details.```  **systemctl status apache2.service** ● apache2.service - The Apache HTTP Server    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)    Active: failed (Result: exit-code) since Tue 2019-07-09 09:11:20 CEST; 2min 44s ago      Docs: https://httpd.apache.org/docs/2.4/   Process: 11763 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)  jul 09 09:11:20 vek-ubuntu apachectl[11763]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this mes jul 09 09:11:20 vek-ubuntu apachectl[11763]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80 jul 09 09:11:20 vek-ubuntu apachectl[11763]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80 jul 09 09:11:20 vek-ubuntu apachectl[11763]: no listening sockets available, shutting down jul 09 09:11:20 vek-ubuntu apachectl[11763]: AH00015: Unable to open logs jul 09 09:11:20 vek-ubuntu apachectl[11763]: Action 'start' failed. jul 09 09:11:20 vek-ubuntu apachectl[11763]: The Apache error log may have more information. jul 09 09:11:20 vek-ubuntu systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE jul 09 09:11:20 vek-ubuntu systemd[1]: apache2.service: Failed with result 'exit-code'. jul 09 09:11:20 vek-ubuntu systemd[1]: Failed to start The Apache HTTP Server.  **journalctl -xe** jul 09 09:13:05 vek-ubuntu dhclient[11812]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 3 (xid=0x992da85e) jul 09 09:13:08 vek-ubuntu dhclient[11812]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 3 (xid=0x992da85e) jul 09 09:13:11 vek-ubuntu dhclient[11812]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 4 (xid=0x992da85e) jul 09 09:13:12 vek-ubuntu kernel: r8169 0000:04:00.0 enp4s0: rtl_txcfg_empty_cond == 0 (loop: 666, delay: 100). jul 09 09:13:15 vek-ubuntu dhclient[11812]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 4 (xid=0x992da85e) jul 09 09:13:19 vek-ubuntu dhclient[11812]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 9 (xid=0x992da85e) jul 09 09:13:28 vek-ubuntu dhclient[11812]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 21 (xid=0x992da85e) jul 09 09:13:50 vek-ubuntu dhclient[11812]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 14 (xid=0x992da85e) jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <warn>  [1562656430.1354] dhcp4 (enp4s0): request timed out jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1355] dhcp4 (enp4s0): state changed unknown -> timeout jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1522] dhcp4 (enp4s0): canceled DHCP transaction, DHCP client pid 11812 jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1523] dhcp4 (enp4s0): state changed timeout -> done jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1530] device (enp4s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed') jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <warn>  [1562656430.1547] device (enp4s0): Activation: failed for connection 'Trådbunden anslutning 1' jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1554] device (enp4s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') jul 09 09:13:50 vek-ubuntu avahi-daemon[1302]: Withdrawing address record for fe80::37d5:905b:6570:1eaa on enp4s0. jul 09 09:13:50 vek-ubuntu avahi-daemon[1302]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::37d5:905b:6570:1eaa. jul 09 09:13:50 vek-ubuntu avahi-daemon[1302]: Interface enp4s0.IPv6 no longer relevant for mDNS. jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1588] policy: auto-activating connection 'Trådbunden anslutning 1' (4aaddc78-ded2-3c3d-820d-51833c7b4b11) jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1593] device (enp4s0): Activation: starting connection 'Trådbunden anslutning 1' (4aaddc78-ded2-3c3d-820d-51833c7b4b11) jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1595] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1599] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1603] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1607] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds) jul 09 09:13:50 vek-ubuntu NetworkManager[1308]: <info>  [1562656430.1621] dhcp4 (enp4s0): dhclient started with pid 11868 jul 09 09:13:50 vek-ubuntu avahi-daemon[1302]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::37d5:905b:6570:1eaa. jul 09 09:13:50 vek-ubuntu avahi-daemon[1302]: New relevant interface enp4s0.IPv6 for mDNS. jul 09 09:13:50 vek-ubuntu avahi-daemon[1302]: Registering new address record for fe80::37d5:905b:6570:1eaa on enp4s0.*. jul 09 09:13:50 vek-ubuntu dhclient[11868]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 3 (xid=0x4b037477) jul 09 09:13:53 vek-ubuntu dhclient[11868]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 7 (xid=0x4b037477) jul 09 09:14:00 vek-ubuntu dhclient[11868]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 10 (xid=0x4b037477) jul 09 09:14:02 vek-ubuntu kernel: r8169 0000:04:00.0 enp4s0: rtl_txcfg_empty_cond == 0 (loop: 666, delay: 100). jul 09 09:14:10 vek-ubuntu dhclient[11868]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 20 (xid=0x4b037477) jul 09 09:14:30 vek-ubuntu dhclient[11868]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 10 (xid=0x4b037477) jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <warn>  [1562656475.1356] dhcp4 (enp4s0): request timed out jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1357] dhcp4 (enp4s0): state changed unknown -> timeout jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1683] dhcp4 (enp4s0): canceled DHCP transaction, DHCP client pid 11868 jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1684] dhcp4 (enp4s0): state changed timeout -> done jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1691] device (enp4s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed') jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <warn>  [1562656475.1705] device (enp4s0): Activation: failed for connection 'Trådbunden anslutning 1' jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1712] device (enp4s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') jul 09 09:14:35 vek-ubuntu avahi-daemon[1302]: Withdrawing address record for fe80::37d5:905b:6570:1eaa on enp4s0. jul 09 09:14:35 vek-ubuntu avahi-daemon[1302]: Leaving mDNS multicast group on interface enp4s0.IPv6 with address fe80::37d5:905b:6570:1eaa. jul 09 09:14:35 vek-ubuntu avahi-daemon[1302]: Interface enp4s0.IPv6 no longer relevant for mDNS. jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1744] policy: auto-activating connection 'Trådbunden anslutning 1' (4aaddc78-ded2-3c3d-820d-51833c7b4b11) jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1750] device (enp4s0): Activation: starting connection 'Trådbunden anslutning 1' (4aaddc78-ded2-3c3d-820d-51833c7b4b11) jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1751] device (enp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1756] device (enp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1760] device (enp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1763] dhcp4 (enp4s0): activation: beginning transaction (timeout in 45 seconds) jul 09 09:14:35 vek-ubuntu NetworkManager[1308]: <info>  [1562656475.1776] dhcp4 (enp4s0): dhclient started with pid 11895 jul 09 09:14:35 vek-ubuntu avahi-daemon[1302]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::37d5:905b:6570:1eaa. jul 09 09:14:35 vek-ubuntu avahi-daemon[1302]: New relevant interface enp4s0.IPv6 for mDNS. jul 09 09:14:35 vek-ubuntu avahi-daemon[1302]: Registering new address record for fe80::37d5:905b:6570:1eaa on enp4s0.*. jul 09 09:14:35 vek-ubuntu dhclient[11895]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 3 (xid=0xe6c8bb5e) jul 09 09:14:38 vek-ubuntu dhclient[11895]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 8 (xid=0xe6c8bb5e)   

Issue hosting html page and apache2 refusing to restart

When I tried to restart Apache to test my webpage I got this error and I don’t know how to fix it.

 systemctl status apache2.service ● apache2.service - LSB: Apache2 web server    Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)   Drop-In: /lib/systemd/system/apache2.service.d            └─apache2-systemd.conf    Active: active (running) (Result: exit-code) since Tue 2019-06-18 18:10:36 PDT; 43min ago      Docs: man:systemd-sysv-generator(8)   Process: 13037 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)   Process: 13821 ExecReload=/etc/init.d/apache2 reload (code=exited, status=1/FAILURE)   Process: 13139 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)    CGroup: /system.slice/apache2.service            ├─13154 /usr/sbin/apache2 -k start            ├─13157 /usr/sbin/apache2 -k start            ├─13158 /usr/sbin/apache2 -k start            ├─13159 /usr/sbin/apache2 -k start            ├─13160 /usr/sbin/apache2 -k start            └─13161 /usr/sbin/apache2 -k start  Jun 18 18:53:54 john-john apache2[13821]:  * Reloading Apache httpd web server apache2 Jun 18 18:53:54 john-john apache2[13821]:  * Jun 18 18:53:54 john-john apache2[13821]:  * The apache2 configtest failed. Not doing anythin Jun 18 18:53:54 john-john apache2[13821]: Output of config test was: Jun 18 18:53:54 john-john apache2[13821]: AH00526: Syntax error on line 3 of /etc/apache2/sit Jun 18 18:53:54 john-john apache2[13821]: ServerAlias only used in <VirtualHost> Jun 18 18:53:54 john-john apache2[13821]: Action 'configtest' failed. Jun 18 18:53:54 john-john apache2[13821]: The Apache error log may have more information. Jun 18 18:53:54 john-john systemd[1]: apache2.service: Control process exited, code=exited st  ``````````  

How would Japanese people react to someone refusing to say “itadakimasu” for religious reasons?

So, it’s my understanding that in Japan it’s considered to be polite to say “itadakimasu” before eating. From what I’ve read, it seems that the meaning of this phrase derives from Buddhist and Shinto religious concepts, however, which gives rise to this question: how would the typical Japanese person respond to a foreigner (who might be a Christian, Muslim, or a member of some similar monotheistic faith) who refused to say it (as politely as possible) and cited religious reasons to do so?

Uwsgi/nginx unix socket refusing connections

I have a python project that I am trying to serve with uWSGI and Nginx. I’m trying to connect the two with a Unix IPC socket (debian stretch), but the socket refuses connections whenever Nginx tries to connect to it. It’s not an issue of proper permissions or Nginx being pointed to the wrong location; I’ve already checked for that. What I believe may be the problem is that Nginx/the system does not see it as the proper socket file type to connect to. I considered this as a possibility when I did ls -l on the directory containing it, and it showed “-rw-rw-r–“. With all the sockets I’ve seen, they have some variation of that with a “s” where the first hyphen is. How can I fix this issue?

iPod Click Wheel (4G Classic) crashes in the manner of refusing to wake up and I can’t seem to figure out why

I’ve had this iPod since 2009 and it’s been running a 32GB CF card via adapter. For seven years I’ve had no problems with it until I wanted to rebuild my library from scratch. All the files I’ve had before on it work just fine but if I want to add new tracks there’s a high possibility the iPod will only play so many tracks before refusing to wake up when it goes to sleep. There aren’t any tracks the iPod refuses to play so I can’t find any specific track that’s tripping something in the iPod’s memory causing it to fault consistently. All tracks are 128Kbps AAC with VBR.

Things I’ve tried: 1. A different motherboard, CF card and adapter. The issue still persists. I’ve not used a standard hard disk. 2. I’ve replaced the battery. 3. Converted all the new tracks to WAV and converted them to AAC to shed ID3 tags and possibly errors with the MP3 codec within iTunes (i.e. some tracks play garbled in iTunes but are completely fine in other players).

I’m just curious if anyone else has stumbled upon this before.

Piston refusing to make me a window

I’m trying to make the Rust game engine Piston work on my Ubuntu 14.04 laptop. I have already got it up and running on my desktop and I’ve made Snake there. So I know the basics of how to use the package.

However, on my (somewhat older) laptop, piston refuses to do what it’s supposed to do. Here is my main.rs:

extern crate piston_window; use piston_window::*;  fn main() {     let mut window : PistonWindow = WindowSettings::new(             "Piston-test", (200, 200))         .exit_on_esc(true)         .build()         .unwrap();      while let Some(e) = window.next() {         match e {             Event::Loop(Loop::Render(_)) => {                 window.draw_2d(&e, |_context, graphics| {                     clear([1.0, 0.5, 0.5, 1.0], graphics);                 });             }             _ => {}         }     } } 

and in my Cargo.toml, I have

[dependencies] piston_window = "0.83.0" 

The program compiles fine, but when it runs, the window it’s supposed to create appears for a split second, then disappears again. The error I get is a panic at the unwrap() call, with the message

GL context creation failed

Now, I’ve googled this, and it’s a problem I’m not alone in having. I have tried what I came across. I’ve tried specifying opengl(OpenGL::V3_2) and V2_1 on the WindowSettings, and I’ve tried using glutin_window instead of piston_window (glutin itself, and the example they have on their GitHub seems to run just fine, though).