Network scripts question -
by Bob Goodwin
I have two F-15 computers. Box6 has the following files while box9
has only /etc/sysconfig/network-scripts/ifcfg-lo, both are using
NetworkManager.
[bobg@box6 ~]$ ll /etc/sysconfig/network-scripts/ifcfg-*
-rw-r--r--. 3 root root 577 Jun 22 18:16
/etc/sysconfig/network-scripts/ifcfg-eth1
-rw-r--r--. 1 root root 254 Apr 27 13:17
/etc/sysconfig/network-scripts/ifcfg-lo
-rw-r--r--. 3 root root 577 Jun 22 18:16
/etc/sysconfig/network-scripts/ifcfg-p2p1
I can ssh from box6 to box9 but not from box9 to box6. Either one
will ping the other, stopping the fire wall does not have any effect.
Any suggestions, what to look for?
Bob
.--
12 years, 8 months
mail / mailx question
by Paul Allen Newell
I am running an F14 system which is pretty much out-of-the-box except I
have the machine hardcoded to 192.168.2.13 to keep my network happy.
I see all sorts of uses of 'mail [...] root@localhost' which work great
when I look in /var/spool/mail/root. I have read the mail / mailx
documentation and tried sending mail to both root and my local account
and it works great. The man pages keep using examples like
"joe(a)somewhere.com", but when I try that with my email account
(name(a)whatever.edu), it fails (as in nothing happens and I sometimes get
resend errors). I can ping whatever.edu successfully.
I am certain this is a stupid pilot error, but can't figure it out.
Any suggestions?
Thanks in advance,
Paul
12 years, 8 months
Living with Systemd
by Arthur Dent
Hello All,
I am gradually getting used to systemd. I can now just about force my
fingers to type "systemctl restart httpd.service" even though my brain
is itching to write "service httpd restart" and I find this cheatsheet
to be very useful:
http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet
However, there is one thing I find *incredibly* frustrating and that is
the paucity of information when things go wrong.
When I am tinkering with some app or other and I mess something up (as I
often do), being told that the app has "entered a failed state", but not
*WHY* it failed is very unhelpful. At least with SystemV you would be
told that it's because a file is missing, permission problem, config
error... etc.
Looking into /var/log/messages is no help (it just repeats the same
message) and very often the program's own logs are of no use because the
app has not started logging.
I have looked at man systemctl but can see no "verbose" (or similar)
switch.
I find that the only way I can troubleshoot a failing process is to
start the program directly from its executable, or by manually running
the init.d script. Then I get some useful information as to why the
program failed, and fix it.
Jul 22 00:01:11 mydomain systemd[1]: httpd.service: control process exited, code=exited status=1
Jul 22 00:01:11 mydomain systemd[1]: Unit httpd.service entered failed state.
The above error was caused by one rule in the thousands of mod-security
rules that I had just updated.
Starting httpd directly from the init script I found this:
Syntax error on line 91 of /etc/httpd/modsecurity.d/base_rules/modsecurity_crs_20_protocol_violations.conf:
Error creating rule: Unknown variable: REQBODY_ERROR
and I could see exactly what I needed to fix.
Am I missing something? Is there a way to get helpful error messages
with systemd that I don't know about - or are we stuck with "code=exited
status=1"?
Mark
12 years, 8 months
Debugging cups problems
by Alan Cox
I've moved one server box to FC15 to get support for various bits of
newer hardware. Aside from preupgrade not working (blowing up near the
end and not adding the boot entries) its mostly behaving as a server.
One thing that has totally broken though is the cups printing support.
Its a networked printer (Dell 3115N multi-function) and I've tried it
with the 3100 drivers included in Fedora 15 and with the Dell drivers
that worked before.
In both cases I see
D [06/Jul/2011:19:01:49 +0100] [Job 2] backendRunLoop(print_fd=0,
device_fd=5, s nmp_fd=6, addr=0x7f40de2b8a48, use_bc=1,
side_cb=0x7f40ddb48cd0) D [06/Jul/2011:19:01:49 +0100] [Job 2] Read 8192
bytes of print data... D [06/Jul/2011:19:01:49 +0100] [Job 2] Wrote 8192
bytes of print data... D [06/Jul/2011:19:01:49 +0100] [Job 2] Read 8192
bytes of print data... D [06/Jul/2011:19:01:49 +0100] [Job 2] Wrote 8192
bytes of print data... D [06/Jul/2011:19:01:49 +0100] [Job 2] Read 8192
bytes of print data... D [06/Jul/2011:19:01:49 +0100] [Job 2] Set
job-printer-state-message to "Unable to write print data: Broken pipe",
current level=ERROR D [06/Jul/2011:19:01:49 +0100] [Job 2] Print file
sent, waiting for printer to f inish...
D [06/Jul/2011:19:01:49 +0100] [Job 2] Backend returned status 1 (failed)
D [06/Jul/2011:19:01:49 +0100] [Job 2] Printer stopped due to backend
errors; pl ease consult the error_log file for details.
D [06/Jul/2011:19:01:49 +0100] [Job 2] End of messages
But no real further info anywhere else which is making it a bit hard to
nail down what is going on.
I can print happily from an FC14 box on the same network.
12 years, 8 months
Progress?
by David A. De Graaf
With the advent of Fedora 15 we have lost features that have been the
bedrock of a reliable system - all the name of "progress".
Here are my pleas to the Fedora development team:
Give us back a single entry of LUKS passphrase for all filesystems.
Give us back an intelligible display of boot progress.
Give us back the fsck progress crawl so we know boot isn't hung.
Give us back a simple way to see what services are running, started,
and failed in a concise format.
Give us back system configuration tools that work in a root window.
Give us back the mount command - that shows only the actual physical
filesystems that are mounted - in a readable format.
Give us back a humanly comprehensible device naming system.
Give us back the reboot command that doesn't hang the system, along with
informative progress status reports.
Give us back nfs and autofs that work, and which can shutdown if network
connectivity has failed.
Give us back USB wireless interfaces that work reliably.
Give us back a filesystem that obeys the access rules for root so that
~/.gvfs is readable/searchable for backups.
Give us back kernels that don't abort instead of an abrt reporting
system.
Give us back the assurance of never having to reboot.
Give us back the legendary reliability that was the hallmark of
Linux and Fedora.
--
David A. De Graaf DATIX, Inc. Hendersonville, NC
dad(a)datix.us www.datix.us
If I were two-faced, would I be wearing this one?
-- Abraham Lincoln
12 years, 8 months
What happend to aes586?
by Clemens Eisserer
Hi,
I've recently switched to dmcrypt with aes cipher, which works quite well
except for beeing a little bit slow (~40mb/s read/write), where even weaker
CPUs in an old comparison I found yield ~60-80mb/s.
A few times AES586 is mentioned beeing a hand optimized assembler version of
the generic AES module, but I wasn't able to find it. Is it not part of the
Fedora15 default kernel, or has it been removed from vanilla as well?
Thank you in advance, Clemens
12 years, 8 months
first FC15 boot -- oh no!
by Gerhard Magnus
When I try logging on after booting up FC15 for the first time... oh no!
It's extremely irritating to get a cute message that offers no useful
information whatsoever.
My impression from cursory scanning of this list is that gnome 3 doesn't
work with a lot of hardware configurations. Is this likely the problem,
and if so is there a way I can log on to KDE, which presumably still
works? Any suggestions as to how to proceed would be appreciated.
Jerry
12 years, 8 months
More RAM not recognized -
by Bob Goodwin
This Dell DM4700 came with 2-256 mb strips, some time ago I added
2-1 gb strips for a total of 2.5 gb.
This morning I replaced the 256 mb strips with 2-2 gb for a total of
6. The bios setup screen shows 6 gb but apparently Linux is only
using half that amount, not much of an improvement!:
[bobg@box6 ~]$ free -m
total used free shared
buffers cached
Mem: 3022 719 2303 0
31 265
-/+ buffers/cache: 422 2600
Swap: 4575 0 4575
This is an up to date F-15 32 bit configured as I want it.
[bobg@box6 ~]$ uname -a
Linux box6 2.6.38.8-35.fc15.i686 #1 SMP Wed Jul 6 14:46:26 UTC 2011
i686 i686 i386 GNU/Linux
Must I install the 64 bit version to take advantage of the memory?
If so perhaps I could upgrade the present install to 64 and keep my
configuration or do I have to bite the bullet and do a new install.
Bob
--
12 years, 8 months
F15: firefox reload button - grey or green?
by John Horne
Hello,
I recently upgraded (via fresh installs) both my home PC and work PC to
Fedora 15. No problems generally, but one odd thing I noticed.
In firefox the reload button is a green colour at work, but grey at
home. Not 'greyed-out' as the 'stop' button is, but just a grey in
colour. I assumed this was just some sort of theme difference, but
looking through a sorted list of the installed rpms from the work and
home PCs I really cannot see what might be causing this. Customizing the
firefox toolbar makes no difference (I can add/remove things but not
change their colour). If I click on the button the current web page
reloads, but the button itself does not change at all on either PC.
(Unlike the 'stop' button which turns red whilst the page reloads, and
then becomes greyed-out when it has finished.)
Anyone any ideas? As said, it's not a hindrance or am that bothered by
it, I'm more just curious as to why it has happened at all.
Thanks,
John.
--
John Horne, University of Plymouth, UK
Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
12 years, 8 months
