Or sign in with one of these services
&&03/15/17
Post bugs here:
We ask - you vote - we implement. Or not. Easy as that.
Advertisement
Advertisement
Do not post questions here. This is for RELEASES ONLY
No posts here yet
No posts here yet
185.00 EUR of 80.00 EUR goal reached.
Advertisement
& February 12
& November 25, 2016
& September 17, 2016
& September 16, 2016
& August 17, 2016
Member Statistics
Total Members
Most Online
August 5, 2016
Joined 5 hours ago
Forum Statistics
Total Topics
Total Posts
Started March 24
Started Monday at 12:45 PM
Started March 12
Started Wednesday at 06:36 PM
Started 3 hours ago
Started 13 hours ago
Started 12 hours ago
Started 14 hours ago
Started 6 hours ago
Started March 9
Started 12 hours ago
Started 9 hours ago
Started 10 hours ago
Started March 17
Started 19 hours ago经典老儿歌如何让现在孩子唱得不尴尬
唱丢手绢，不知手绢用途；唱小燕子，没见过真燕子……经典儿歌遇到新问题，怎么样才能把它们唱到现在孩子的心里去？
澎湃新闻记者 孔德虎 唐燕丽
澎湃新闻APP下载
/newsDetail_forward_
把你最喜欢的栏目添加到这里来哦.Net（48）
将开发完的程序发布到内网的站点中() ，在进行访问的时候出现如下错误：&Customization could not be loaded because the application domain could not be created。但将文件另存到其他位置的时候，就可以访问。
经过排查，最后发现是Excel 2007 安全设置的问题。将此Web地址添加到Excel 2007 的信任列表中即可。但默认情况下Excel 2007 是不允许添加 web站点的，所以需要在注册表中手动添加。注册表位置：HKEY_CURRENT_USER/Software/Microsoft/Office/12.0/Excel/Security/Trusted Locations
参考知识库
* 以上用户言论只代表其个人观点，不代表CSDN网站的观点或立场
访问：122756次
积分：1763
积分：1763
排名：第19929名
原创：38篇
转载：56篇
评论：12条
(1)(1)(1)(4)(1)(1)(1)(2)(3)(1)(1)(1)(1)(1)(1)(3)(2)(1)(6)(2)(2)(1)(4)(1)(1)(3)(8)(4)(6)(9)(22)mod_proxy_balancer requires 2 bytes of random data during
start/restart which will result in a blocking read of /dev/random.
On some virtualized systems, or systems where some other process is exhausting
/dev/random, startup may hang until enough entropy can be gathered
by the system.
A quick measure of /dev/random response time and variance is the
following shell command:
do /usr/bin/time dd if=/dev/urandom of=- bs=2 count=1 2&&1|grep -i R sleep 2; done
Consult your operating system vendor if /dev/random response time is an issue for IHS startup, or disable
mod_proxy_balancer.
In V8R5 and earlier, the adminctl script must be updated if the
PidFile in conf/admin.conf is changed.
The normal
apachectl does not maintain a separate definition of the PID file.
When running 64-bit IHS on Solaris, IHS cannot be launched if the environment
variable LD_LIBRARY_PATH_64 has been set prior to running apachectl
and it was not setup to include the $IHSROOT/lib and $IHSROOT/gsk8/lib.
Siteminder customization to IHS startup scripts can cause startup failures.
Siteminder configuration often adds a file named ca_wa_env.sh to $IHSROOT/bin/envvars or $IHSROOT/bin/apachectl.
This script often modifies the LIBPATH environment variable. It must not prepend any items to the
LIBPATH, only append.
Particularly risky items prepended to the LIBPATH include e.g.
/opt/freeware or /lib (the latter was observed due to an unresolved variable such as ${FOO}/lib).
Siteminder can crash during startup, without providing much feedback,
without AIX APAR IV08416 on AIX 6.1 and later (IV16240 for AIX 7.1)
If the APAR cannot be applied, this test/workaround confirms it's the same issue:
# in bin/envvars
TZ=America/New_York
SSL0114E: Initialization error, Error processing cryptography.
In IHS v8 or later, this can occur if your KeyFile has an empty password.
You must set a non-null password for your KeyFile in Ikeyman.
SSL0115E: Initialization error, Error validating ASN fields in certificate
In IHS v8 or later, with GSKit 8.0.14.11 or earlier, this misleading error
can be issued when a KDB stash file is corrupted or has been overwritten by
$IHSROOT/bin/sslstash.
After GSKit 8.0.14.11, this will be reported as
"SSL0104E: GSK could not initialize, Invalid password for keyfile.".
If you're using PKCS11 cryptographic offload, re-stash your secondary KDB password with Ikeyman,
and choose a new output location for the $IHSROOT/bin/sslstash
command and SSLSTashFile directive.
Truncate or delete the WebSphere Plugin log (http_plugin.log) if it has
reached 2GB in size.
Check the documentation for
and see if any of them apply to the problem.
Error message referring to the text "ap_cache_cacheable_hdrs_out" when starting IHS.
Make sure the LoadModule directive for mod_cache is un-commented and precedes
the LoadModule directive for mod_mem_cache.
Error message referring to the text "ap_proxyerror" or
"proxy_hook_scheme_handler".
Make sure the LoadModule directive for mod_proxy is un-commented and precedes the
LoadModule directive for mod_proxy_http, mod_proxy_connect, and mod_proxy_ftp.
/dev/null must be writable by the userid that runs apachectl. Generally, /dev/null is world-writable
by default.
The httpd command cannot be used directly because
library paths must be set up beforehand so that support libraries are
found in the IHS lib directory.
apachectl command, in conjunction with the
IHSROOT/bin/envvars file, sets up the library
paths as necessary.
Here are some example console messages that you can
see on different platforms when the httpd is used
directly or there is a problem with the
IHSROOT/bin/envvars file or a customer-modified
apachectl command does not work:
ld.so.1: /opt/IBMIHS20420/bin/httpd: fatal: libaprutil.so.0: open failed: No such file or directory
/usr/lib/hpux64/dld.so: Unable to find library 'libaprutil-0.sl.9'.
Could not load program
/opt/IBMIHS/bin/httpd:
Dependent module libaprutil-0.so could not be loaded.
Could not load module libaprutil-0.so.
Error was: No such file or directory
# /opt/IBMIHS/bin/httpd -f /opt/IBMIHS/conf/httpd.conf
Syntax error on line 161 of /opt/IBMIHS/conf/httpd.conf:
Cannot load /opt/IBMIHS/modules/mod_cgid.so into server:
/opt/IBMIHS/modules/mod_cgid.so: undefined symbol: ihs_os_pipe_put_ex
Syntax error on line 845 of /opt/IBMIHS/conf/httpd.conf:
Cannot load /opt/IBMIHS/modules/mod_ibm_ssl.so into server:
/opt/IBMIHS/modules/mod_ibm_ssl.so:
undefined symbol: apr_socket_iol_push (or ihs_socket_iol_push)
On Linux, you can get this same symptom while using apachectl if you
make $IHS_ROOT/bin/httpd setuid or setgid because LD_LIBRARY_PATH
will be ignored by the operating system. Making IHS binaries setuid or
setgid is not supported.
# apachectl start
(98)Address already in use: make_sock: could not bind to address [::]:80
no listening sockets available, shutting down
Unable to open logs
Check for overlapping Listen directives in httpd.conf.
Ensure that the port specified in the error message isn't
already in use.
netstat or lsof can be
used for this.
$ netstat -an | grep :80
0 0.0.0.0:80
# lsof -ni :80
DEVICE SIZE NODE NAME
TCP *:http (LISTEN)
25812 nobody
TCP *:http (LISTEN)
25814 nobody
TCP *:http (LISTEN)
25815 nobody
TCP *:http (LISTEN)
In IHS configurations where mod_cgid is loaded, some types of
crashes during initialization can leave an httpd process running. In
these cases, the stranded httpd process will be running as the
non-root userid specified by the User directive and
will have a parent pid of 1. This process should be removed with
kill -TERM.
Possible initialization problems which can leave an httpd process
running include:
The WebSphere plugin logfile specified in the plugin-cfg.xml
may have grown to 2 gigabytes, leading to a crash during
initialization.
If the log file is 2GB or greater in size, remove the log
file, terminate any stranded httpd processes, and re-start IHS.
/usr/IBMHttpServer2/bin#./apachectl start
[Thu Jul 22 23:47:15 2004] [crit] (78)Connection timed out: alloc_listener: failed to set up sockaddr for ::
Syntax error on line 130 of /usr/IBMHttpServer2/conf/httpd.conf:
Listen setup failed
The text of the message can also be "A remote host did not respond
within the timeout period." instead of "Connection timed out".
This is caused by a failure of the AIX resolver function
getaddrinfo() when passed certain parameters. It can be avoided by
disabling IPv6 listening sockets in IHS. That is done by changing a
Listen directive such as
Listen 0.0.0.0:80
AIX APAR IY57293 resolves this problem for AIX 5.2.
IY57365 is the equivalent for AIX 5.1.
This may be caused by IPv6 resolver lookups.
Try this possible
solution, which is to skip IPv6 lookups for IHS.
Add this to the end of ihsroot/bin/envvars:
NSORDER=local4,bind4
export NSORDER
Now try to start IHS and see if the problem is resolved.
Apply PM11586 in 6.1.0.33 and later if Siteminder won't start with SSL enabled.
After installing IBM HTTP Server 6.1 onto a Windows 64-bit OS (Windows 2003 or Windows 2008),
the web server may not start
when using the 'Start HTTP Server' shortcut icon on the 'Start' menu.
You may also see a message displayed that is similar to the following:
"The item 'apache.exe' that this shortcut refers to has been
changed or moved, so this shortcut will no longer work properly."
When IBM HTTP Server 6.1 is installed to the default location under C:\Program Files
on a 64-bit Windows OS, the shortcut icons are created incorrectly.
When this occurs, the icons are created with values such as:
"C:\Program Files(x86\IBM\HTTPServer,\)\bin\apache.exe" -w -n
"IBM HTTP Server 6.1" -k start
"C:Program Files(x86/IBM/HTTPServer,\)\bin"
There are several problems in these strings:
The right parentheses for (x86 is in the wrong position
There typically should be a space between 'Program Files' and '(x86)'
after 'HTTPServer' should not be present
The 'Start in:' value should have a forward slash after the C:
These can be resolved by editing the values as follows:
Select 'Start->All Programs->IBM HTTP Server V6.1' and right-click 'Start HTTP Server'
Select 'Properties'
Select the 'Shortcut' tab page if not there
Edit both the 'Target:' and 'Start in:' values.
Assuming the original values looked identical to the examples above, then you would fix them
by editing to look like:
"C:\Program Files (x86)\IBM\HTTPServer\bin\apache.exe" -w -n
"IBM HTTP Server 6.1" -k start
"C:/Program Files (x86)/IBM/HTTPServer/bin"
If your actual paths are different, then adjust as needed.
You simply need to edit them to be
valid paths.
(The Start in: path should work with either forward slashes or backslashes.)
Repeat the above for the 'Stop HTTP Server' shortcut.
You should also check the following items.
These may have similar path problems that need to be corrected.
Edit them to be valid paths as needed.
(The base part of the values should look similar to the good values shown above.)
httpd.conf file entries:
'ServerRoot'
'DocumentRoot'
The Plugin entries
Paths within the Plugin config file
Paths within the Admin Console config
Additional information can be found in the 'Restriction' section of the
InfoCenter page.
Since the IHS problem is in the install of the base 6.1 package, it cannot be resolved via a fixpack.
The solution is to perform the edits described above, or to install to a path that doesn't contain parentheses in the path string.
The problem does not occur with the newer IBM HTTP Server V7.
This can occur at startup for IHS 6.1.0.47 if the PI31516 interim fix is applied without first upgrading GSKit to a minimum required version as described
in the Prerequisites section of the
Upgrade the global GSKit as specified to resolve the problem.
This can also occur on 6.1 on Windows if an older GSKit is installed and set to be preferred
globally via the PATH environment variable.
This can occur on 7.0 or later on Unix if $IHSROOT/bin/envvars is tampered with or LD_LIBRARY_PATH/LIBPATH is manipulated
to find a global GSKit installation from another product.
This can occur if any of the following statements is true:
IHS is already running.Solution: No action required.
A stale httpd.pid file exists in the logs directory, and the PID is already being used by another process. This can happen if IHS was not gracefully shutdown.
Solution: Remove the stale httpd.pid file.
(Linux only) A stale httpd.pid file exists in the logs directory, and the PID is already being used by a Light Weight Process (LWP). This can happen if IHS was not gracefully shutdown. LWP PIDs can be viewed using the command: ps -efL
Solution: Remove the stale httpd.pid file.
Step 3: Determine a minimal configuration which has the problem
There are several features which commonly are related to startup
Determination of which feature, if any, triggers the
startup problem will result in faster diagnosis of the problem.
features are:
third-party modules
WebSphere plug-in
mod_ibm_ssl
mod_ibm_ldap
Additionally, the use of https transports in the WebSphere
plug-in configuration may trigger the problem.
To find the minimal configuration, disable all of these features.
If the problem still occurs, it is not triggered by any of these
features, but leave them disabled anyway to keep the configuration
If the problem does not occur, then enable one of these
features at a time to find the trigger.
When enabling the WebSphere
plug-in, try it with and without https transports defined, in
order to determine if the use of SSL is the trigger.
If the problem does not occur without a third-party module loaded,
contact the vendor of that module for further diagnosis.
Step 4: OS-specific workarounds
Step 4.1 Linux
Try setting one of these environment
variables prior to running apachectl start to see if the
problem is resolved:
Mechanism to switch to an alternate C++ run-time library (GSkit 7)
RHEL AS2.1
export LD_PRELOAD=/usr/lib/libstdc++-libc6.2-2.so.3
RHEL AS3.0
export LD_ASSUME_KERNEL=2.2.5export LD_PRELOAD=/usr/lib/libstdc++-libc6.2-2.so.3
Other Linux/x86
export LD_PRELOAD=/usr/lib/libstdc++-libc6.2-2.so.3
export LD_PRELOAD=/usr/lib/libstdc++-libc6.1-2.so.3
The problem symptom can show up like this:
$ bin/apachectl -k start -f conf/ssl.conf
bin/apachectl: line 87: 15476 Aborted
(core dumped) $HTTPD $ARGV
If this resolves the problem, that is your permanent solution, and
gathering further information is not necessary.
Step 4.2 HP-UX/PA-RISC
Apply these two HP-UX patches which resolve incompatibilies with
the SSL library provided with IBM HTTP Server (GSKit), and confirm
that the startup problem is resolved:
PHSS_26946
PHSS_33033
Step 5: Gathering information about the system and the IHS
installation
Follow the instructions for the System and web server information tool
to create a package to upload.
Step 6: Disable mod_cgid until the problem is resolved
This step applies only to IHS 2.0 or above on Unix and Linux
At initialization, mod_cgid creates a separate child process to
handle CGI requests.
During some types of startup failures, this
child process is left stranded when IHS crashes.
mod_cgid should be
disabled until the problem is resolved so that the mod_cgid child
process does not have to be manually terminated, and so that it does
not appear that IHS startup has hung since an httpd process (the
mod_cgid child) will remain running.
To disable mod_cgid, comment out this line in the configuration
LoadModule cgid_module modules/mod_cgid.so
Also, if you're using the ScriptSock,
ScriptLog, ScriptLogBuffer, or
ScriptLogLength, make sure they aren't active when
mod_cgid is disabled.
Such directives can be automatically disabled
when mod_cgid is disabled by using a IfModule
container, as shown below:
&IfModule mod_cgid.c&
Scriptsock
logs/cgisock
&/IfModule&
Step 7: Turn on detailed logging until the problem is
IBM HTTP Server
Edit the configuration file (usually httpd.conf) and
set the value of the LogLevel directive to
If SSL support is enabled, add the
SSLTrace directive to the bottom of the configuration
WebSphere plug-in
Edit the configuration file (usually plugin-cfg.xml)
and change LogLevel to Trace. For
&Log LogLevel="Trace" Name="/opt/IBM/WebSphere/AppServer/logs/http_plugin.log"/&
Step 8: Gathering traces, console messages, and coredumps
Make sure coredumps are allowed:
# ulimit -c unlimited
If the problem is related to SSL, set the following
environment variables via &ihsinst&/bin/envvars or the windows
control panel:
GSK_TRACE_FILE_NUMBER=1
export GSK_TRACE_FILE_NUMBER
# This following setting should only be used for suspected crashes
GSKTRACE_NOBUFFERING=YES
export GSKTRACE_NOBUFFERING
GSK_TRACE_FILE_SIZE=
export GSK_TRACE_FILE_SIZE
Start IHS to create the failure:
# /path/to/apachectl start
(If necessary, substitute your normal way of starting IBM HTTP
Note that apachectl is the only supported
mechanism for starting IHS 2.0 and above on Unix and Linux
Cut and paste the actual command used to startup IHS, as well as
any messages which appeared on the console, into a file.
Check for a coredump.
The location can vary by system
configuration and platform.
Check in the current directory for a file
called core* or search the system for a file called
core* and with a current timestamp.
On Solaris, run the
coreadm command to see if an alternate location or
filename pattern has been specified for coredumps.
On AIX 5.2 and
above, run syscorepath -g to see if an alternate location
has been specified for coredumps.
If a coredump was generated, follow the instruction here to extract information from it.
Step 9: Get syscall trace of startup
Last, get a syscall trace of startup to show what processing
occurred before the failure.
The following table shows the command to
use for your platform.
AIX 5.2 and above
truss -o /tmp/ihs_startup -d -f startup-command
truss -o /tmp/ihs_startup -f startup-command
strace -o /tmp/ihs_startup -f startup-command
Linux on SUSE for 64-bit zSeries (s390x)
strace32 -o /tmp/ihs_startup -f startup-command (RPM: strace-32bit)
truss -o /tmp/ihs_startup -f startup-command
tusc -o /tmp/ihs_startup -f startup-command
Before running this, unset the environment variables
GSK_TRACE_FILE and GSKTRACE_NOBUFFERING.
Replace startup-command with the command used to
start IHS.
After the startup failure occurs, the syscall trace will
be in file /tmp/ihs_startup.
Step 10: Sending information to IBM
The information to send to IBM includes:
Information to send
nothing (no data collected)
your statement on which optional features, if any, were
required to trigger the startup problem
whether or not the specified /usr/lib/libstdc++.X file existed
whether or not this setting resolved the problem
the ServerConfig.xxx directory
nothing (no data collected)
the IBM HTTP Server and WebSphere plug-in configuration files,
after being modified to enable tracing
the GSKit trace in /tmp/gsktrace (if the problem was related to SSL)
a cut-and-paste of all messages that appeared on the console after
running apachectl start
IHS error log
WebSphere plug-in trace file (if the problem was related to
WebSphere plug-in)
CrashDoc.xxx directory (if a coredump was generated)
the syscall trace file /tmp/ihs_startupdb:: 4.30::Could not load file or assembly XXXXX or one of its dependencies. An attempt was made to load a program with an incorrect format pz
Widget settings form goes here