09-14-2009
Hi,
I can only see one error here - complaining that your filesystem is too small ...
I would recommend to extend it until the coredump fits in ... and than try to analyze it with dbx
All others look at least to me like rather normal boot messages
Rgds
zxmaus
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all! I am praying someone can help me. I have been trying to install dual nics on my FreeBSD box. In my attempts I edited my RC.CONF file. I must have editing something wrong, because during the boot sequence, my machine gets through bringing up most of the services then it stops and gets... (5 Replies)
Discussion started by: ezekiel61
5 Replies
2. AIX
Hi Guys,
We are migrating AIX 5.1 to AIX 5.3. With this upgrade the C/C++ compiler is also upgraded to Visual Age C++ 6.0.
After upgrading, when we tried to (re)compile our programs (since ibm open library classes are not going to work with new compiler), we are getting so many errors with no... (2 Replies)
Discussion started by: satguyz
2 Replies
3. UNIX for Dummies Questions & Answers
First of all, I'd like to preface this post by relaying that I have considerable experience with FreeBSD but I'm a Linux newb. I've been attempting to compile linux-2.6.29.3 from source and I'm having some problems and have a few newb questions...
a) First of all, my kernel won't boot, it fails... (0 Replies)
Discussion started by: urbanriot
0 Replies
4. Solaris
Help needed please! I see the following scsi errors during boot up. The server eventually boots up successfully. Please let me now how to fix these errors:
Executing last command: boot
Boot device: disk File and args:
SunOS Release 5.8 Version Generic_117350-62 64-bit
Copyright 1983-2003 Sun... (4 Replies)
Discussion started by: pingmeback
4 Replies
5. Solaris
Hi all.
I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'.
I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies
6. AIX
Hi Admins,
# lspath -H -l hdisk2
status name parent
Enabled hdisk2 fscsi0
Enabled hdisk2 fscsi0
Missing hdisk2 fscsi2
Missing hdisk2 fscsi2
Enabled hdisk2 fscsi0
Enabled hdisk2 fscsi0
Enabled hdisk2 fscsi2
Missing hdisk2 fscsi2
Multi path IO status is shown as Missing for... (2 Replies)
Discussion started by: newaix
2 Replies
7. AIX
Good afternoon there,
One of my friend gave me an old IBM 44P Model 170 (I've planned to use it to learn AIX that I don't know at all) (I know a bit GNU/Linux (Debian, Archlinux, Red Hat, Slackware)).
But, unfortunately, the computer doesn't start properly and I don't have any idea why ;(.
... (6 Replies)
Discussion started by: firstpost
6 Replies
8. AIX
Hi Can any suggest me how to work on this particular issue i am facing.
Below is the error message received on vio servers.
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
4B436A3D 0326102912 T H fscsi1 LINK ERROR
4B436A3D 0325212712 T H fscsi1 LINK ERROR
4B436A3D... (2 Replies)
Discussion started by: ganiiee
2 Replies
9. AIX
Hello,
Could you please check the below errors. I found these errors in AIX LPAR syslogs.
auth|security:err|error sshd error: Could not load host key: /etc/ssh/ssh_host_ecdsa_key
daemon:err|error syslog: slp: 0660-059 Impossible to get local interface for distant address 10.x.x.x. errno... (2 Replies)
Discussion started by: Kumar7997
2 Replies
LEARN ABOUT XFREE86
systemd-sysctl.service
SYSTEMD-SYSCTL.SERVICE(8) systemd-sysctl.service SYSTEMD-SYSCTL.SERVICE(8)
NAME
systemd-sysctl.service, systemd-sysctl - Configure kernel parameters at boot
SYNOPSIS
/lib/systemd/systemd-sysctl [OPTIONS...] [CONFIGFILE...]
systemd-sysctl.service
DESCRIPTION
systemd-sysctl.service is an early boot service that configures sysctl(8) kernel parameters by invoking /lib/systemd/systemd-sysctl.
When invoked with no arguments, /lib/systemd/systemd-sysctl applies all directives from configuration files listed in sysctl.d(5). If one
or more filenames are passed on the command line, only the directives in these files are applied.
In addition, --prefix= option may be used to limit which sysctl settings are applied.
See sysctl.d(5) for information about the configuration of sysctl settings. After sysctl configuration is changed on disk, it must be
written to the files in /proc/sys before it takes effect. It is possible to update specific settings, or simply to reload all
configuration, see Examples below.
OPTIONS
--prefix=
Only apply rules with the specified prefix.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXAMPLES
Example 1. Reset all sysctl settings
systemctl restart systemd-sysctl
Example 2. View coredump handler configuration
# sysctl kernel.core_pattern
kernel.core_pattern = |/libexec/abrt-hook-ccpp %s %c %p %u %g %t %P %I
Example 3. Update coredump handler configuration
# /lib/systemd/systemd-sysctl --prefix kernel.core_pattern
This searches all the directories listed in sysctl.d(5) for configuration files and writes /proc/sys/kernel/core_pattern.
Example 4. Update coredump handler configuration according to a specific file
# /lib/systemd/systemd-sysctl 50-coredump.conf
This applies all the settings found in 50-coredump.conf. Either /etc/sysctl.d/50-coredump.conf, or /run/sysctl.d/50-coredump.conf, or
/usr/lib/sysctl.d/50-coredump.conf will be used, in the order of preference.
See sysctl(8) for various ways to directly apply sysctl settings.
SEE ALSO
systemd(1), sysctl.d(5), sysctl(8),
systemd 237 SYSTEMD-SYSCTL.SERVICE(8)