|
Since you're using http then that would be port 80. If you've installed a web server on PC2, then you may already have port 80 open. You can check to make sure that the port is open using nc
nc -z -w 1 IpPC2 80; echo $? $? is the return value of the last command, so if it's 0 then the connection was successful. Anything other than 0, and the connection failed. Make sure you've got a web server running on PC2. You can do that using netstat
[k5054@localhost: ~$ sudo netstat -tlnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/init
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 623/sshd: /usr/sbin
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 659/cupsd
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 664/postgres
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1001/exim4
tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 1422/sshd: k5054@pt
tcp6 0 0 :::111 :::* LISTEN 1/init
tcp6 0 0 :::22 :::* LISTEN 623/sshd: /usr/sbin
tcp6 0 0 ::1:631 :::* LISTEN 659/cupsd
tcp6 0 0 ::1:5432 :::* LISTEN 664/postgres
tcp6 0 0 ::1:25 :::* LISTEN 1001/exim4
tcp6 0 0 ::1:6010 :::* LISTEN 1422/sshd: k5054@pt You want to look for something listening on port 80 - which I do not have running in the above screen grab
Keep Calm and Carry On
|
|
|
|
|
Thank you very much.
With your instructions I have been able to verify that port 80 is open on PC2 and that Apache is listening on port 80.
$ sudo netstat -tlnp
Activate Internet connections (only servers)
. . .
tcp6 0 0 :::80 :::* LISTEN 967/apache2
. . .
Later I was able to find an error in a configuration file of PC1, which was the cause of the error.
|
|
|
|
|
Message Closed
modified 15-May-23 19:06pm.
|
|
|
|
|
You probably deleted the partition but didn't update your grub configs. As far as how to update Grub... I bet Google knows.
Jeremy Falcon
|
|
|
|
|
Hi,
I am running Slackware current with a 5.18.7 kernel. The motherboard it was running on has been switched, and because I was presented with a grub-rescue prompt (only after the motherboard switch, worked perfect prior to this) I chose to reinstall. Now what is happening is the grub-rescue prompt it displayed on the screen for a second or 2 and then the normal grub menu shows up and boots properly. I can't figure out how to fix this for the main drive was formatted and partitioned during install. It has 2 partitions on it a 4GB swap and the remainder of the 2TB drive for /. The second drive is also a 2TB drive both same make and model and has 1 partition on it /home which was not formatted during install, so all the files and so forth remain intact after the user is re-added. I should mention I am using grub version 2.06. Any help on this would be greatly appreciated.
|
|
|
|
|
Example:
$ ./0-current_working_directory
/root/alx-system_engineering-devops/0x00-shell_basics
$
Repo:
GitHub repository: alx-system_engineering-devops
Directory: 0x00-shell_basics
File: 0-current_working_directory
|
|
|
|
|
You seem to have forgotten to ask a question.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Message Closed
modified 15-May-23 19:06pm.
|
|
|
|
|
|
Message Closed
modified 15-May-23 19:06pm.
|
|
|
|
|
According to my reading of the documentation that should work, so I am afraid I have no more ideas.
|
|
|
|
|
You may or may not have access to a GRUB environment block (of which you make no mention).
Quote: For safety reasons, this storage is only available when installed on a plain disk (no LVM or RAID), using a non-checksumming filesystem (no ZFS), and using BIOS or EFI functions (no ATA, USB or IEEE1275).
grub-mkconfig uses this facility to implement ‘GRUB_SAVEDEFAULT’ (see Simple configuration).
GNU GRUB Manual 2.06
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Message Closed
modified 15-May-23 19:06pm.
|
|
|
|
|
Quote: The environment block is a preallocated 1024-byte file, which normally lives in /boot/grub/grubenv (although you should not assume this). At boot time, the load_env command (see load_env) loads environment variables from it, and the save_env (see save_env) command saves environment variables to it. From a running system, the grub-editenv utility can be used to edit the environment block.
GNU GRUB Manual 2.06: Environment block
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Message Closed
modified 15-May-23 19:06pm.
|
|
|
|
|
I just tried this and it works correctly. Whatever is happening on your system is unique to you, and may have something to do with previous questions which suggest that your installation is not very stable.
|
|
|
|
|
Isn't this something you can see from the source code?
That's the the great advantage of open source projects: If the system doesn't behave the way you want it to, you have the full freedom to go into the source code and modify it the way you want.
|
|
|
|
|
Message Closed
modified 15-May-23 19:06pm.
|
|
|
|
|
Member 14968771 wrote: As a "user" why should I (have) to do that ?
Because it is Free and Open Source Software.
It is given to you so that you can fix it yourself. That is what the free-ness and open-ness is about. You may of course ask your friends to fix it for you, or even pay someone to fix it (although that sort of kills the "free" idea, at least in the sense of "free beer").
When you accept a "free" offer that is financed by ads and commercials, then you are the product being sold.
When you accept "free" and open sources software, then you are the maintainer of that software.
This is 101 FOSS.
|
|
|
|
|
Message Closed
modified 15-May-23 19:06pm.
|
|
|
|
|
|
Message Closed
modified 15-May-23 19:06pm.
|
|
|
|
|
Member 14968771 wrote: for example "device_desc" and "dd" are same...
Maybe, but that is not a rule that you can rely on.
|
|
|
|
|
Message Closed
modified 15-May-23 19:06pm.
|
|
|
|
|
Short answer is you don't need to know. When linking your program with -lbluetooth should be enough, if it's installed in the usual place. Depending on what your development environment is, you can use pkg-config to tell you what flags you need to use to find headers and libs e.g
k5054@localhost:~$ pkg-config --cflags bluez
k5054@localhost:~$ pkg-config --libs bluez
-lbluetooth
k5054@localhost:~$ This tells us that we don't need any additional flags for compilation, and only need to add -lbluetooth when linking.
If you really want to know where the lib is, you can use dpkg to tell you where it is
k5054@localhost:~$ dpkg -S libbluetooth | grep .so
libbluetooth3:amd64: /usr/lib/x86_64-linux-gnu/libbluetooth.so.3
libbluetooth3:amd64: /usr/lib/x86_64-linux-gnu/libbluetooth.so.3.19.3
libbluetooth-dev:amd64: /usr/lib/x86_64-linux-gnu/libbluetooth.so
k5054@localhost:~$ Note that debian/ubuntu uses the target architecture as part of the filename for libraries, so for a PI with a 32 bit Raspberry Pi OS, the path is /usr/lib/arm-linux-gnueabihf/libbluetooth.so.3, and it would be different again for a PI with a 64-bit OS, or an i386, MIPS, etc.
Keep Calm and Carry On
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
