Visit Our UNIX and Linux User Community

Lose IP after TL Update

Thread Tools Search this Thread
Operating Systems AIX Lose IP after TL Update
# 8  
Old 08-13-2013
I do not believe the activation of the IP stack should be dependent on any application. That said, I did have issues myself, and it came down to things I had done "in innocence", i.e. user error in changes to /etc/inittab and/or /etc/rc.d/* scripts.

In my case I did always get an IP address, just lacked some daemons such as ssh.

Besides rebooting several times to try and observe what was going wrong I also used the output of the command alog -o -t console and alog -o -t boot to read messages from programs to find that missing depenadancy.

Unfortunately, for you, I do not remember the specifics - this was too long ago. But I do recommend checking your alog outputs for hints about what is going on, error messages, etc..

mkdev -l en0; mkdev -l inet0 will do what startup should have done (assuming single interface en0. If more interfaces do them all, then inet0.

Previous Thread | Next Thread
Test Your Knowledge in Computers #198
Difficulty: Easy
Bash ranked in the top 20 programming languages according to the TIOBE Index for October 2019.
True or False?

5 More Discussions You Might Find Interesting

1. AIX

Lose default gateway

hello iv 2 AIX P720 machine aix 6.1 6100-02-03-0909 both , hacmp ver both machine connect to the same switch. after networking fault , one of the machines lost his default gateway !!! what can be the reason ? thx (4 Replies)
Discussion started by: ariec
4 Replies

2. AIX

AIX with 2 Net Interfaces lose connectivity

hi guys We have a AIX Server with TSM installed. This server has en0 for administration purposes and we have en1 for backup stuff. en0 subnet 10.10.10.x en1 subnet 10.10.20.x The issue we are having is all of a sudden the LPARs we are backing up lose connectivity to the AIX-TSM Server.... (23 Replies)
Discussion started by: karlochacon
23 Replies

3. Shell Programming and Scripting

Does a variable lose its value outside the loop in shell script?

hi, when we assign a variable inside a for loop or while loop in a shell script, does it loses its value after comming out of the loop. i am facing this issue. can anyone help me?? (8 Replies)
Discussion started by: Little
8 Replies

4. UNIX for Dummies Questions & Answers

Trying to lose XP & Install Suse 10.1

Hello, I bought a second pc to install Suse 10.1 on. It came with Xp pro installed on it. I downloaded Suse 10.1, burned 5 CD's, changed bios to boot from the cdrom, restart the pc & Xp loads. Any suggestions? Thank You (1 Reply)
Discussion started by: Nick7269
1 Replies

5. Solaris

Will I lose drivers while upgrading to ten?

I'm running Solaris 8 with a box I just got and it has a VGA connection. Will I lose the VGA driver while upgrading to 10? I don't have a Sun Monitor so if so I'll be screwed. Tia (0 Replies)
Discussion started by: PapaPark
0 Replies
cgi-fcgi - bridge from CGI to FastCGI SYNOPSIS
cgi-fcgi -f cmdPath cgi-fcgi -bind -connect connName cgi-fcgi -start -connect connName appPath [nServers] cgi-fcgi -connect connName appPath [nServers] DESCRIPTION
cgi-fcgi is a CGI/1.1 program that communicates with an already-running FastCGI application in order to respond to an HTTP request. cgi-fcgi is also capable of starting a FastC- GI
application. When you invoke cgi-fcgi as cgi-fcgi -f cmdPath then cgi-fcgi opens the file at cmdPath and reads its arguments from that file. cgi-fcgi will skip lines that begin with the comment character #. The first non-comment line should contain valid arguments in one of the other three forms. The -f form of cgi-fcgi is designed for Unix systems whose exec(2) family of system calls supports the execution of command interpreter files. For instance, if a file with execute permission contains the text #! /bin/cgi-fcgi -f -connect /httpd/root/sock/app /httpd/root/bin/app the effect is the same as executing /bin/cgi-fcgi -connect /httpd/root/sock/app /httpd/root/bin/app When you invoke cgi-fcgi as cgi-fcgi -bind -connect connName the connName argument is either the path name of a Unix do- main listening socket or a host:port pair. If connName contains a colon, it is assumed to be host:port. cgi-fcgi performs a connect(2) using connName. If the connect succeeds, cgi- fcgi forwards the CGI environment variables and stdin data to the FastCGI application, and forwards the stdout and stderr data from the application to cgi-fcgi's stdout (most likely connected to a Web server). When the FastCGI application signals the end of its response, cgi-fcgi flushes its buffers and exits, and the Web server completes the http response. When you invoke cgi-fcgi as cgi-fcgi -start -connect connName appPath [nServers] then cgi-fcgi performs the function of starting one or more FastCGI application processes. The connName argument speci- fies either the path name of the Unix domain listening socket that cgi-fcgi will create, or is "localhost:NNN" where NNN is the port number of the TCP/IP listening socket that cgi-fcgi will create on the local machine. (cgi-fcgi will not create processes on remote machines.) After cgi-fcgi creates the listening socket, it forks nServers copies of a process running the executable file appPath. If nServers is omitted, the effect is as if the value ";1" had been specified. The processes share the single listen- ing socket. When you invoke cgi-fcgi as cgi-fcgi -connect connName appPath [nServers] cgi-fcgi performs -bind and then, if necssary, performs -start and repeats the -bind. That is, cgi-fcgi first operates as if the command had been cgi-fcgi -bind -connect connName If the connect fails, cgi-fcgi tries cgi-fcgi -start -connect connName appPath [nServers] and finally retries cgi-fcgi -bind -connect connName In this form, cgi-fcgi does not support TCP/IP connections. ENVIRONMENT VARIABLES
The usual CGI ones, but they are not interpreted by cgi-fc- gi. SEE ALSO
FGCI_accept(3) BUGS
cgi-fcgi doesn't generate useful HTTP responses in case of error, and it generates no response at all when run as start-fcgi. On Digital UNIX 3.0 systems the implementation of Unix Do- main sockets does not work when such sockets are stored on NFS file systems. Symptom: cgi-fcgi may core dump or may exit with status 38. Work-around: store sockets in local file systems (/tmp often works) or use TCP/IP. On AIX systems the implementation of listening sockets does not support socket sharing, and the standard FastCGI application libraries can't synchronize access to AIX lis- tening sockets. Work-around: Don't use the nServers argument on AIX. HISTORY
Copyright (c) 1996 Open Market, Inc. See the file "LICENSE.TERMS" for information on usage and redistribution of this file, and for a DISCLAIMER OF ALL WARRANTIES. $Id: cgi-fcgi.1,v 1997/09/16 15:36:26 stanleyg Exp $

Featured Tech Videos