Hi Sir,
My NIC is working fine because when I try to choose the grub option
ubuntu, linux 2.6.31-14-generic-pae (on /dev/sda5)
I can ping users in LAN but I can not restart network and ssh.
but if choose the option
ubuntu, linux 2.6.31-14-generic-pae
thats the time the network is down even when I try to up the network
doesn't goes up.
my GRUB options:
ubuntu, linux 2.6.31-14-generic-pae
ubuntu, linux 2.6.31-14-generic-pae (recovery mode)
memory test (memtest 86+)
memory test (memtest 86+, serial console 115200)
ubuntu, linux 2.6.31-14-generic-pae (on /dev/sda5)
ubuntu, linux 2.6.31-14-generic-pae (on /dev/sda5) (recovery mode on
/dev/sda5)
What do you think sir?
Thanks,
AL
On 9/14/2011 6:51 PM, fooler mail wrote:
> hi al,
>
> as what i said below.. you have two problems...
>
> fix your network interface card problem first... when it is not in
> RUNNING state.. a strong indication that your nic link state is not
> up... if it is not up or not in running state.. it wont accept any
> traffic from any hosts...
>
> here is what you gonna do for a simple test...
>
> 1. get a working crossover cable
> 2. connect one end of that crossover cable to your laptop or pc and
> assign an IP address 192.168.0.1 with a netmask 255.255.255.0.. just
> ignore gateway, dns and other settings..
> 3. connect the other end of that crossover cable to your server eth1
> interface card.. make sure you know which one is eth1 as i assume you
> have multiple nics in your server.. if you are not sure.. just try to
> insert one at a time to all those nic ports until you see RUNNING
> state in eth1... if you cant see running state.. then you have a
> broken nic..
> 4. if it is in running state... inside your server.. with (or without)
> firewall rules.... just remove or flush that firewall table by running
> this command "iptables -F" in root
> 5. in your laptop/pc... ping your server... ping 192.168.0.2
>
> at this point.. i assume you will get a reply.... run your ssh server
>
> root# service ssh stop
> root# service ssh start
>
> from your laptop/pc... ssh 192.168.0.2 (use IP not FQDN)
>
> the rest.. you know what to do to fix your problem...
>
>
> fooler.
>
> On Wed, Sep 14, 2011 at 5:05 PM, AL Pelias<[email protected]> wrote:
>> Hi Sir,
>>
>> whats the status of my instruction?
>>
>> all services are down even when I try to start ssh manually it goes up
>> but still cant use it because of the network is down but when I start
>> the network I received the message:
>>
>> the script you are attempting to invoke has been converted to an upstart
>> job.
>>
>> FYI.
>>
>> Thanks,
>> AL
>>
>>
>> On 9/14/2011 10:39 AM, fooler mail wrote:
>>> whats the status of my instruction?
>>>
>>> fooler.
>>>
>>> On Sat, Sep 10, 2011 at 7:48 AM, fooler mail<[email protected]>
>>> wrote:
>>>> On Fri, Sep 9, 2011 at 3:20 PM, AL Pelias<[email protected]>
>>>> wrote:
>>>>> Hi Sir,
>>>>>
>>>>> run the following at root prompt:
>>>>>
>>>>> 1. runlevel
>>>>> N 2
>>>>>
>>>>> 2. ifconfig
>>>>> Pls see attached:ifconfig.jpg
>>>>>
>>>>> 3. netstat -ln
>>>>> Pls see attached:netstat_ln.jpg
>>>>>
>>>>> 4. netstat -rn
>>>>> pls see attached:netstat_rn.jpg
>>>>>
>>>>>
>>>>> sorry for the blurred jpg files.
>>>> dont worry it needs a 3D glass to see it clearly :->
>>>>
>>>> runlevel is 2 which is normal to ubuntu server...
>>>>
>>>> netstat -rn looks good while its default gateway is 192.168.0.4..
>>>>
>>>> ifconfig shows that your eth1 is up with an ip adddress of 192.168.0.2
>>>> and netmask of 255.255.255.0..
>>>>
>>>> netstat -ln shows that no processes are listening to any TCP ports..
>>>> thats include your ssh tcp port 22...
>>>>
>>>> you have two problems here...
>>>>
>>>> 1. eventhough your eth1 is "UP" but it is not in "RUNNING" state... as
>>>> you can see in your ifconfig output.. lo0 is only UP and RUNNING...
>>>> if an interface is not in running state.. it wont accept any data...
>>>> check your cable for any breakage and reinsert both sides (network
>>>> card and switch port) to tighten up...
>>>>
>>>> after that make sure your eth1's state look like this:
>>>>
>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>>
>>>> 2. your ssh (and other services) didnt come up after boot.. even if
>>>> your eth1 is not in running state as long as it is in UP state... ssh
>>>> will bind to eth1 interface as well as to loopback interface (as
>>>> loopback interface is always on all the time and assuming ssh is bind
>>>> to any interface)..
>>>>
>>>> check your service status and look for ssh if it is mark as run during
>>>> boot up...
>>>>
>>>> root# service --status-all
>>>>
>>>> you can manually run it...
>>>>
>>>> root# service ssh start
>>>>
>>>> for more info running a service....
>>>>
>>>> https://help.ubuntu.com/community/UbuntuBootupHowto
>>>>
>>>> fooler.
>>>>
>>> _________________________________________________
>>> Philippine Linux Users' Group (PLUG) Mailing List
>>> http://lists.linux.org.ph/mailman/listinfo/plug
>>> Searchable Archives: http://archives.free.net.ph
>>>
>> _________________________________________________
>> Philippine Linux Users' Group (PLUG) Mailing List
>> http://lists.linux.org.ph/mailman/listinfo/plug
>> Searchable Archives: http://archives.free.net.ph
>>
> _________________________________________________
> Philippine Linux Users' Group (PLUG) Mailing List
> http://lists.linux.org.ph/mailman/listinfo/plug
> Searchable Archives: http://archives.free.net.ph
>
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
http://lists.linux.org.ph/mailman/listinfo/plug
Searchable Archives: http://archives.free.net.ph
