Sponsored Content
Special Forums UNIX and Linux Applications Infrastructure Monitoring unable to shutdown solaris 10 Post 302399174 by alienkidmj12 on Friday 26th of February 2010 02:33:12 PM
Old 02-26-2010
hi, nothing commented out there, ive tidied up my ifconfig now, all that works, as my hostname.bge0 was not matching with the hosts file. i think the error in question started occuring when i ran inetadm -f against the inet.conf file, it seems to have changed other info which i cannot locate, im now getting

Code:
# Feb 26 19:04:23 midnight-sol inetd[348]: The inetd_start method of instance svc:/network/netbios-ns/udp:default isn't a regular file

and
Code:
 
Feb 26 19:00:23 midnight-sol /usr/lib/snmp/snmpdx: unable to get my IP address: gethostbyname(midnight-sol) failed [h_errno: host not found(1)]
Last login: Fri Feb 26 18:43:48 on console
Feb 26 19:00:24 midnight-sol last message repeated 9 times
Feb 26 19:00:24 midnight-sol svc.startd[7]: application/management/snmpdx:default failed repeatedly: transitioned to maintenance (see 'svcs -xv' for details)

my hosts file is as follows
Code:
#
# Internet host table
#
127.0.0.1       localhost loghost midnight-sol
::1     localhost
192.168.0.33    midnight-sol-net1 net1
192.168.0.34    midnight-sol-net2 net2
192.168.0.35    midnight-sol-net3 net3
192.168.0.36    midnight-sol-net4 net4

and my ifconfig now shows
Code:
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000 
bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 192.168.0.33 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:4d:d2:11 
bge1: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 3
        inet 192.168.0.34 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:4d:d2:12 
bge2: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 4
        inet 192.168.0.35 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:4d:d2:13 
bge3: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 5
        inet 192.168.0.36 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:4d:d2:14

system still takes ages to shutdown, is there anything ican run to provide output which might help the situation ?? thanks

Last edited by Scott; 02-26-2010 at 03:39 PM.. Reason: Code tags please...
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Help unable to shutdown- RPC problems

I seem to have consistent problems shuting down whichever init state I use basically I get the following errors messages followed by a return to the prompt # shutdown -i6 -g0 -y Shutdown started. Tue Oct 1 09:47:03 BST 2002 Broadcast Message from root (pts/1) on hermione Tue Oct 1... (3 Replies)
Discussion started by: MBGPS
3 Replies

2. UNIX for Dummies Questions & Answers

Help unable to shutdown- RPC problems

Help unable to shutdown- RPC problems I seem to have consistent problems shuting down whichever init state I use basically I get the following errors messages followed by a return to the prompt # shutdown -i6 -g0 -y Shutdown started. Tue Oct 1 09:47:03 BST 2002 Broadcast Message from... (1 Reply)
Discussion started by: vviscomi
1 Replies

3. Solaris

Unable to shutdown and start machine

Hello. I have just installed solaris on my PC (standalone). It allows to reboot. But IF I shut down and the restart by pressing the button - It does not show my solaris OS and I am then forced to perform fresh installation. Could you please let me know the fix for it - So that shutdown and... (3 Replies)
Discussion started by: panchpan
3 Replies

4. Solaris

Restart/Shutdown the Solaris from SC>

Hi Experts, I am running solris 9. Sun-Fire 880. How do i shutdowon the whole server using ALOM i.e sc> console. If the server is down or somehow hang How do i Restart from sc> //purple (6 Replies)
Discussion started by: thepurple
6 Replies

5. UNIX for Dummies Questions & Answers

Script to force Oracle database shutdown when shutdown immediate does not work

I have Oracle 9i R2 on AIX 5.2. My Database is running in shared server mode (MTS). Sometimes when I shutdown the database it shutsdown cleanly in 4-5 mints and sometimes it takes good 15-20 minutes and then I get some ora-600 errors and only way to shutdown is by opening another session and... (7 Replies)
Discussion started by: aixhp
7 Replies

6. Solaris

Solaris 10 container graceful shutdown?

Hi, I've got a UPS connected to my Solaris 10 machine and I'm planning to run containers/zones on there. At the moment if the UPS agent sends the signal to the solaris machine to shutdown, all the apps shutdown gracefully and then the host goes down. If I setup containers for the apps, does... (9 Replies)
Discussion started by: fastexit
9 Replies

7. UNIX for Advanced & Expert Users

Solaris shutdown and boot history

Hello. I'm trying to get a Solaris (SunOS 5.10) shutdown and boot history. Unfortunately the /var/adm/wtmpx file does not cover the period I want to trace. It's been reset. Therefore the command, "last" (or "last reboot") does not reach back far enough. Additionally the /var/adm/messages*... (4 Replies)
Discussion started by: etlpkby
4 Replies

8. Solaris

Remote shutdown Solaris

Hi I want to shutdown my remote Solaris servers from XP machine. i want their must be a script file which i run all of the server go down. i try telnet but it ask for passwd. help me out. (4 Replies)
Discussion started by: akhaliq22
4 Replies

9. Shell Programming and Scripting

Automatic shutdown and startup of Tomcat in Solaris

Dear Experts , I want to stop and Start tomcat at the time of shutdown and startup of our server . I was trying to stop tomcat with following command # su - dm -c "/export/home/Finder/FinderWeb/jakarta-tomcat-3.3.1a/bin/shutdown.sh" but i am getting following error. Please suggest .... (1 Reply)
Discussion started by: Amit.saini333
1 Replies

10. UNIX for Beginners Questions & Answers

Linux SuSE SLES 8 error..unable to issue shutdown command

the only way we can power off is if we actually press power button on server. Running on HP DL-G4. from root, when we issue command it just returns to root prompt. (1 Reply)
Discussion started by: amexboy
1 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 12:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy