Sponsored Content
Operating Systems Solaris Reboot, System is Frozen at setting interface for multicast HELP Post 302155991 by don123 on Monday 7th of January 2008 01:14:39 AM
Old 01-07-2008
hi eyukins

i also got same error msg....have you get rid of this problem...let me know solution...




Quote:
Originally Posted by eyukins
I'm not an advanced user by any strech, that being said here is my problem:


I ran "reboot" on a sun blade 2500

When loading up it runs through the usual routine, checking disks, filesystems and then it locks up
after the following message:


*****

starting rpc services: rpcbind done.
Setting default IPv4 interface for multicast: add net 224.0/4: gateway ekss-unix
1

***

and then there is no activity what so ever. Please help.

It's not a server or anything, just a cad station. How can I get back to the login screen?

Any help would be greatly appreicated.
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Intermitent System Reboot's

Hi all, Just started holidays (ya!) and Murphy's Law has kicked in already (doh!). I'm looking after (when at work) two SCO 5.0.5 Systems running on Netfinity 5500 Servers (Model # 8662-3RY). Every once and a while the production server just reboot's itself. There is no mention of a cause... (8 Replies)
Discussion started by: Cameron
8 Replies

2. Programming

Joining multicast group on IPADDR_ANY - which interface?

Hello all, I have the following question: if you join a multicast group (with setsockopt() and IP_ADD_MEMBERSHIP) and specify INADDR_ANY as network interface to join on, the kernel is supposed to choose which interface to use (if there are multiple network interfaces, of course). Does... (2 Replies)
Discussion started by: AlexI
2 Replies

3. UNIX for Dummies Questions & Answers

System Reboot Dates

Hi, Can someone advise me how to find the last system rebooted date(s)? Thanx N Regards, Hush (2 Replies)
Discussion started by: hush
2 Replies

4. AIX

IP setting changes after server reboot

I've recently changed my gateway setting using SMIT. Everything went fine except that the gateway setting kept reverting back to the old one everytime I reboot the server. I'm on AIX 5.2 running p-Series. Thanks for any info. (3 Replies)
Discussion started by: dereklow
3 Replies

5. Solaris

system self reboot

dear all, I have 2 T2000 with solaris 10 and oracle 10g installed on it. these two servers are rebooted by itself. could anyone help me investigate the cause. the message log is attached thanx, (3 Replies)
Discussion started by: fsmadi
3 Replies

6. Solaris

System Reboot Log

Hello Everyone , I am a new member to this forum and came to know about this from so many of my friends . I face one issue last day when suddenly the system got rebooted ( But don,t know why ) . Can someone please help me in investigating this issue as to why the system got rebooted and who... (4 Replies)
Discussion started by: gera_sachin125
4 Replies

7. Linux

xinetd @system reboot

Hi, Once again I came to get rescued in a situation where one of my workstations has this ierd thing that "xinetd" won't start at reboot or shutdown. I have done the follwoing but no change in results. chkconfig --list xinetd xinetd 0:off 1:off 2:on 3:on 4:on 5:on ... (2 Replies)
Discussion started by: harjitsingh
2 Replies

8. Solaris

system reboot procedure

Hi all, i want to know the procedure reboot the server through console if the system is completely down.Please help me if anybody knows this. I would really thanfull to all. regards Krishna Murthy (1 Reply)
Discussion started by: murthy76
1 Replies

9. UNIX for Dummies Questions & Answers

system is frozen

hi there. new problem for me!!! i have been using a Sabayon Linux 3.5 distribution and yesterday when i turned the system on it stopped responding, i mean it freeazed. i was listening to music on Audacious and suddenly the system is ice cold...baby. what to do. Since i've tried 'reiserfsck' the... (0 Replies)
Discussion started by: dvas83
0 Replies
RPCBIND(8)						    BSD System Manager's Manual 						RPCBIND(8)

NAME
rpcbind -- universal addresses to RPC program number mapper SYNOPSIS
rpcbind [-adhiLls] DESCRIPTION
The rpcbind utility is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to make RPC calls on a server on that machine. When an RPC service is started, it tells rpcbind the address at which it is listening, and the RPC program numbers it is prepared to serve. When a client wishes to make an RPC call to a given program number, it first contacts rpcbind on the server machine to determine the address where RPC requests should be sent. The rpcbind utility should be started before any other RPC service. Normally, standard RPC servers are started by port monitors, so rpcbind must be started before port monitors are invoked. When rpcbind is started, it checks that certain name-to-address translation-calls function correctly. If they fail, the network configura- tion databases may be corrupt. Since RPC services cannot function correctly in this situation, rpcbind reports the condition and terminates. The rpcbind utility can only be started by the super-user. OPTIONS
-a When debugging (-d), do an abort on errors. -d Run in debug mode. In this mode, rpcbind will not fork when it starts, will print additional information during operation, and will abort on certain errors if -a is also specified. With this option, the name-to-address translation consistency checks are shown in detail. -h Specify specific IP addresses to bind to for UDP requests. This option may be specified multiple times and is typically necessary when running on a multi-homed host. If no -h option is specified, rpcbind will bind to INADDR_ANY, which could lead to problems on a multi-homed host due to rpcbind returning a UDP packet from a different IP address than it was sent to. Note that when specifying IP addresses with -h, rpcbind will automatically add 127.0.0.1 and if IPv6 is enabled, ::1 to the list. -i ``Insecure'' mode. Allow calls to SET and UNSET from any host. Normally rpcbind accepts these requests only from the loopback interface for security reasons. This change is necessary for programs that were compiled with earlier versions of the rpc library and do not make those requests using the loopback interface. -l Turn on libwrap connection logging. -s Cause rpcbind to change to the user daemon as soon as possible. This causes rpcbind to use non-privileged ports for outgoing connec- tions, preventing non-privileged clients from using rpcbind to connect to services from a privileged port. -w Cause rpcbind to do a "warm start" by read a state file when rpcbind starts up. The state file is created when rpcbind terminates. NOTES
All RPC servers must be restarted if rpcbind is restarted. SEE ALSO
rpcbind(3), rpcinfo(7) LINUX PORT
Aurelien Charbon <aurelien.charbon@bull.net> BSD
September 14, 1992 BSD
All times are GMT -4. The time now is 08:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy