[systemd-devel] systemd-devel Digest, Vol 94, Issue 25
juan alberto cuevas juarez
jalberto1994 at live.com.mx
Sat Feb 24 23:36:47 UTC 2018
Hello, good afternoon, I'm Juan cuevas a student of systems engineering, greetings from Mexico-Guadalajara I have problem in apache2-localhost
last week I had some problems installing redmine, I installed ruby, buidler, rails, passenger, passenger module for apache2 and the necessary dependencies
subsequently I have configured
root @ cuevasalberto-ThinkPad-Edge-E431: / etc / apache2 # vim apache2.conf
adding module:
LoadModule passenger_module /var/lib/gems/2.3.0/gems/passenger-5.2.0/buildout/apache2/mod_passenger.so
<IfModule mod_passenger.c>
PassengerRoot /var/lib/gems/2.3.0/gems/passenger-5.2.0
PassengerDefaultRuby /usr/bin/ruby2.3
</ IfModule>
configure add port 3000 in ports.conf
I follow the steps in the following link
https://gist.github.com/rotexdegba/e39b6b4f85ac580fe5e0434dbb00beb0
Restart apache2 with the command:
sudo service apache2 restart
and it takes the process, I stopped it with control z
The following apache2 error message is from today, taking into account that I have deleted the configurations of the .conf and the link
https://gist.github.com/rotexdegba/e39b6b4f85ac580fe5e0434dbb00beb0
being as from the beginning, but I still have the apache2.conf configuration
root at cuevasalberto-ThinkPad-Edge-E431:/# 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: failed (Result: timeout) since sáb 2018-02-24 15:06:58 CST; 11min ago
Docs: man:systemd-sysv-generator(8)
Process: 7833 ExecStart=/etc/init.d/apache2 start (code=killed, signal=TERM)
CGroup: /system.slice/apache2.service
├─1500 /bin/sh /usr/sbin/apache2ctl start
├─1515 /usr/sbin/apache2 -k start
├─1525 PassengerAgent watchdog
├─7844 /bin/sh /usr/sbin/apache2ctl start
├─7847 /usr/sbin/apache2 -k start
└─7848 PassengerAgent watchdog
feb 24 15:01:58 cuevasalberto-ThinkPad-Edge-E431 systemd[1]: Stopped LSB: Apache2 web server.
feb 24 15:01:58 cuevasalberto-ThinkPad-Edge-E431 systemd[1]: Starting LSB: Apache2 web server...
feb 24 15:01:58 cuevasalberto-ThinkPad-Edge-E431 apache2[7833]: * Starting Apache httpd web server apache2
feb 24 15:01:58 cuevasalberto-ThinkPad-Edge-E431 apache2[7833]: [Sat Feb 24 15:01:58.337147 2018] [so:warn] [pid 7847] AH01574: module passenger_module is already loaded, skipping
feb 24 15:01:58 cuevasalberto-ThinkPad-Edge-E431 apache2[7833]: 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 message
feb 24 15:06:58 cuevasalberto-ThinkPad-Edge-E431 systemd[1]: apache2.service: Start operation timed out. Terminating.
feb 24 15:06:58 cuevasalberto-ThinkPad-Edge-E431 systemd[1]: Failed to start LSB: Apache2 web server.
feb 24 15:06:58 cuevasalberto-ThinkPad-Edge-E431 systemd[1]: apache2.service: Unit entered failed state.
feb 24 15:06:58 cuevasalberto-ThinkPad-Edge-E431 systemd[1]: apache2.service: Failed with result 'timeout'.
ESCOC
I made this configuration today
in mods-available and mods-enabled I have
<IfModule mod_passenger.c>
PassengerRoot /usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini
PassengerDefaultRuby /usr/bin/ruby
</IfModule>
How can I fix the problem of apache2 localhost and can I have redmine on my machine?
________________________________
De: systemd-devel <systemd-devel-bounces at lists.freedesktop.org> en nombre de systemd-devel-request at lists.freedesktop.org <systemd-devel-request at lists.freedesktop.org>
Enviado: viernes, 23 de febrero de 2018 06:00 a. m.
Para: systemd-devel at lists.freedesktop.org
Asunto: systemd-devel Digest, Vol 94, Issue 25
Send systemd-devel mailing list submissions to
systemd-devel at lists.freedesktop.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
systemd-devel Info Page - freedesktop.org<https://lists.freedesktop.org/mailman/listinfo/systemd-devel>
lists.freedesktop.org
This is the main systemd mailing list. The place where technical stuff is discussed and patches should be posted. Mail submission requires subscription.
or, via email, send a message with subject or body 'help' to
systemd-devel-request at lists.freedesktop.org
You can reach the person managing the list at
systemd-devel-owner at lists.freedesktop.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of systemd-devel digest..."
Today's Topics:
1. Why did you set MountFlags=slave in systemd-udevd.service.in
(Hongzhi, Song)
2. Re: Why did you set MountFlags=slave in
systemd-udevd.service.in (Lennart Poettering)
----------------------------------------------------------------------
Message: 1
Date: Thu, 22 Feb 2018 20:52:26 +0800
From: "Hongzhi, Song" <hongzhi.song at windriver.com>
To: <systemd-devel at lists.freedesktop.org>
Subject: [systemd-devel] Why did you set MountFlags=slave in
systemd-udevd.service.in
Message-ID: <2c3136a5-eb82-c201-1230-86c68f8bc332 at windriver.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Hi,
systemd, upstream commit id c2c13f2df42e0691aecabe3979ea81cd7faa35c7
You set MountFlags=slave just for keeping mounts done by udev rules
private to udevd.
So all block device mounted by systemd-udevd is unvisible for host.
I don't know why. And is there any bad effect, if I change slave to shared ?
Thanks for your help.
BR，
Hongzhi.Song
------------------------------
Message: 2
Date: Fri, 23 Feb 2018 12:06:04 +0100
From: Lennart Poettering <lennart at poettering.net>
To: "Hongzhi, Song" <hongzhi.song at windriver.com>
Cc: systemd-devel at lists.freedesktop.org
Subject: Re: [systemd-devel] Why did you set MountFlags=slave in
systemd-udevd.service.in
Message-ID: <20180223110604.GA3336 at gardel-login>
Content-Type: text/plain; charset=us-ascii
On Do, 22.02.18 20:52, Hongzhi, Song (hongzhi.song at windriver.com) wrote:
> Hi,
>
> systemd, upstream commit id c2c13f2df42e0691aecabe3979ea81cd7faa35c7
>
> You set MountFlags=slave just for keeping mounts done by udev rules private
> to udevd.
>
> So all block device mounted by systemd-udevd is unvisible for host.
>
> I don't know why. And is there any bad effect, if I change slave to shared ?
Well, we generally try to run all our services with sandboxes that are
as tight as we can make them. udev can run arbitrary stuff from its
rules hence the sandbox can't be made too tight unfortunately.
MountFlags=slave is essentially a sandboxing setting: it detaches
mount() operations done within the service from the rest of the
system.
While udev rules can do pretty much everything, we do know that doing
mount operations themselves is not the best of ideas, and there are
better approaches. That's because udev rules should be quick, and
mounting isn't necessarily (in particular on dirty fs).
Specifcally, there are three schemes that are much preferable:
1. Use TAG+="systemd", ENV{SYSTEMD_WANTS}+="foobar.mount" in udev
rules to asynchronously pull in mount units from udev rules.
2. Invoke "systemd-mount" from udev rules, which will spawn transient
automount and mount units for devices. This is generally the best
way in particular in embedded applications to deal with
hotpluggable media. It optionally runs fsck before mounting for
you, and it it uses automounts for keeping the actual window when a
device is mounted as brief as possible, in order to maximize the
chance that the file system remains in a fully clean state, since
it's essentially unmounted whenever idle. If you have hotplug media
this means you get the best chance of leaving the fs in a clean
state, and getting it back into a clean state if it evers gets into
an unclean state.
3. Use a daemon such as udisks to manage hotplugs of devices.
That all said, you can also deviate from upstream and simply drop the
MountFlags=slave, but of course, this means you lose compatibility
with upstream on this.
Lennart
--
Lennart Poettering, Red Hat
------------------------------
Subject: Digest Footer
_______________________________________________
systemd-devel mailing list
systemd-devel at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
systemd-devel Info Page - freedesktop.org<https://lists.freedesktop.org/mailman/listinfo/systemd-devel>
lists.freedesktop.org
This is the main systemd mailing list. The place where technical stuff is discussed and patches should be posted. Mail submission requires subscription.
------------------------------
End of systemd-devel Digest, Vol 94, Issue 25
*********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180224/f9fefb70/attachment-0001.html>
More information about the systemd-devel
mailing list