DPKG package error

tpolim008 · 06-10-2018, 07:56 AM

Hello, it appears that there is nothing left behind, this is also the first time I am trying to install it, I've never installed it before.

Code:

root@WelcomeWesley2018:~# ls -la /etc/bind
ls: cannot access '/etc/bind': No such file or directory
root@WelcomeWesley2018:~#

hydrurga · 06-10-2018, 08:19 AM

Thanks for posting that. Hopefully someone else will step up to the plate because I'm not knowledgeable enough about bind and I can't find any bug reports on the issue.

What I would suggest is that you create a completely fresh operating system install in a partition and see if bind installs correctly with that. The "vanilla" approach.

Also, create a bug report with Ubuntu.

tpolim008 · 06-10-2018, 08:43 AM

Thanks for the help and trying this is actually a fairly new fresh install. I did see that there was a bug with bind9 certain versions but not sure how to see which apt-get was trying to install.. Also, I found a walkthru I tried to follow to install bind from source and that as well errored out at the OpenSSL portion... I know I have OpenSSL installed as I have my website redirected to https.... see below and this was the link I was following http://linux-sxs.org/internet_serving/bind9.html

Code:

@WelcomeWesley2018:~/bind-9.12.1-P2$ ./configure --prefix=/usr \
> --sysconfdir=/etc \
> --enable-threads \
> --localstatedir=/var/state \
> --with-libtool \
> --with-openssl=/usr/ssl
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking whether make sets $(MAKE)... yes
checking how to print strings... printf
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert aarch64-unknown-linux-gnu file names to aarch64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert aarch64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking for gawk... no
checking for mawk... mawk
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for getrandom... no
checking for ar... /usr/bin/ar
checking for etags... no
checking for emacs-etags... no
checking for perl5... no
checking for perl... /usr/bin/perl
checking for python... /usr/bin/python
checking python2 version >= 2.7 or python3 version >= 3.2... found
checking python module 'argparse'... found
checking python module 'ply'... not found
checking for python3... /usr/bin/python3
checking python2 version >= 2.7 or python3 version >= 3.2... found
checking python module 'argparse'... found
checking python module 'ply'... not found
checking for python3.5... /usr/bin/python3.5
checking python2 version >= 2.7 or python3 version >= 3.2... found
checking python module 'argparse'... found
checking python module 'ply'... not found
checking for python3.4... no
checking for python3.3... no
checking for python3.2... no
checking for python2... /usr/bin/python2
checking python2 version >= 2.7 or python3 version >= 3.2... found
checking python module 'argparse'... found
checking python module 'ply'... not found
checking for python2.7... /usr/bin/python2.7
checking python2 version >= 2.7 or python3 version >= 3.2... found
checking python module 'argparse'... found
checking python module 'ply'... not found
checking for python support... disabled
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking for ANSI C header files... (cached) yes
checking for fcntl.h... yes
checking for regex.h... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking for sys/mman.h... yes
checking for sys/sockio.h... no
checking for sys/select.h... yes
checking for sys/param.h... yes
checking for sys/sysctl.h... yes
checking for net/if6.h... no
checking for sys/socket.h... yes
checking for net/route.h... yes
checking for linux/netlink.h... yes
checking for linux/rtnetlink.h... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for working volatile... yes
checking for sysctlbyname... no
checking for flexible array members... yes
checking for mmap... yes
checking for seteuid... yes
checking for setresuid... yes
checking for setegid... yes
checking for setresgid... yes
checking for ftello... yes
checking for fseeko... yes
checking for static inline breakage... no
checking for size_t... yes
checking for ssize_t... yes
checking for uintptr_t... yes
checking for socklen_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking for long long... yes
checking for uname... yes
checking for GCC noreturn attribute... yes
checking for struct lifconf... no
checking for kqueue... no
checking epoll support... yes
checking sys/devpoll.h usability... no
checking sys/devpoll.h presence... no
checking for sys/devpoll.h... no
checking devpoll.h usability... no
checking devpoll.h presence... no
checking for devpoll.h... no
checking if unistd.h or sys/types.h defines fd_set... yes
checking whether byte ordering is bigendian... no
checking for GeoIP support... disabled
checking for GSSAPI library... disabled
checking for random device... /dev/random
checking for /dev/random... yes
checking for arc4random... no
checking for arc4random_stir... no
checking for arc4random_addrandom... no
checking whether to build with thread support... yes
checking for pthread_create in -lpthread... yes
checking for sigwait... yes
checking for pthread_attr_getstacksize... yes
checking for pthread_attr_setstacksize... yes
checking for PTHREAD_MUTEX_ADAPTIVE_NP... using adaptive lock type
checking sched.h usability... yes
checking sched.h presence... yes
checking for sched.h... yes
checking for sched_yield... yes
checking for pthread_yield... yes
checking for pthread_yield_np... no
checking for pthread_setname_np... yes
checking for pthread_set_name_np... no
checking for pthread_np.h... no
checking for sysconf... yes
checking for libtool... yes
checking for OpenSSL library... configure: error: "/usr/ssl/include/openssl/opensslv.h" not found

tpolim008 · 06-10-2018, 09:13 AM

Quote:

Originally Posted by hydrurga

Thanks. Note that I said to use the dpkg command only if the original apt command didn't work (it did). The dpkg command turned out to be unnecessary.

Let's have a look to see if there any remnants from previous bind installations that may not have been removed correctly and thus may be causing problems:

Code:

ls -la /etc/bind

I was able to get bind installed from source however it installed to my home directory is there a way that I can move this to a more appropriate location on the server?

hydrurga · 06-10-2018, 09:14 AM

According to the following page, you may also need to install the OpenSSL headers (libssl-dev):

https://superuser.com/questions/3719...-to-fix#371912

I don't know if this particular fix will work, but in general, if something you do produces an error message, search on the internet for that exact error message, i.e. enclosing the error message in quotes (removing any quotes in the message itself if necessary) - that was how I found the above page.

tpolim008 · 06-10-2018, 09:19 AM

Quote:

Originally Posted by hydrurga

According to the following page, you may also need to install the OpenSSL headers (libssl-dev):

https://superuser.com/questions/3719...-to-fix#371912

I don't know if this particular fix will work, but in general, if something you do produces an error message, search on the internet for that exact error message, i.e. enclosing the error message in quotes (removing any quotes in the message itself if necessary) - that was how I found the above page.

LOL we may have found the same stuff... Here is the reported bug code about the versions of BIND as well... My issue now is that I have it installed to my home directory and Id like to move this to a move "common" location if that's possible or is it best to remove it, download the file in a different location and re-run the extraction process?

https://www.experts-exchange.com/art...on-Debian.html

hydrurga · 06-10-2018, 09:21 AM

Quote:

Originally Posted by tpolim008

I was able to get bind installed from source however it installed to my home directory is there a way that I can move this to a more appropriate location on the server?

Nice one.

Were you in your home directory when you built the package? If so, then it probably built it where it lay, and *probably* the whole directory can be moved elsewhere. Or, there could have been an option during the build, either on the command line or in a config file, to set the installation directory.

I would recommend finding out which of these is the case and either reinstalling with the relevant config setting or doing the reinstallation in the target directory, whichever is relevant.

I'm only speaking in generalisations though as I don't know how this particular package works. The documentation is your best bet.

tpolim008 · 06-10-2018, 09:27 AM

Quote:

Originally Posted by hydrurga

Nice one.

Were you in your home directory when you built the package? If so, then it probably built it where it lay, and *probably* the whole directory can be moved elsewhere. Or, there could have been an option during the build, either on the command line or in a config file, to set the installation directory.

I would recommend finding out which of these is the case and either reinstalling with the relevant config setting or doing the reinstallation in the target directory, whichever is relevant.

I'm only speaking in generalisations though as I don't know how this particular package works. The documentation is your best bet.

yea not going to lie looking at the config file it's out of my area I'm guessing it installs where its downloaded in the "make" process it just ripped thru it all and was done..... Further research to continue on my end thank you for the help unless you have any idea to help if I remove the install, and redownload and install where a more logical place would be for the install.

hydrurga · 06-10-2018, 09:35 AM

Quote:

Originally Posted by tpolim008

yea not going to lie looking at the config file it's out of my area I'm guessing it installs where its downloaded in the "make" process it just ripped thru it all and was done..... Further research to continue on my end thank you for the help unless you have any idea to help if I remove the install, and redownload and install where a more logical place would be for the install.

Ok. According to https://kb.isc.org/article/AA-00768/...iguration.html (oldish instructions), it looks like it is just a source code directory, with the actual binaries being installed to the relevant system directory locations during the build procedure, so you should be able to store the source code directory wherever you want.

Let us know how it goes.

tpolim008 · 06-10-2018, 09:48 AM

Quote:

Originally Posted by hydrurga

Ok. According to https://kb.isc.org/article/AA-00768/...iguration.html (oldish instructions), it looks like it is just a source code directory, with the actual binaries being installed to the relevant system directory locations during the build procedure, so you should be able to store the source code directory wherever you want.

Let us know how it goes.

Thanks so would there be a root file system recommended to install this which would logical? Sorry for all the questions as stated at first I’m fairly new learning and not sure of the full structure and learning as I go while building this pi server I see you posted the KB but a glance doesn’t seem to say this would be best place for install...

hydrurga · 06-10-2018, 10:11 AM

Quote:

Originally Posted by tpolim008

Thanks so would there be a root file system recommended to install this which would logical? Sorry for all the questions as stated at first I’m fairly new learning and not sure of the full structure and learning as I go while building this pi server I see you posted the KB but a glance doesn’t seem to say this would be best place for install...

For the locations of the binaries etc., I would just go with the defaults (the document mentions that the binaries get placed in /usr/local/bin and /usr/local/sbin by default, you don't need to worry about all that, it's automatically done as part of the build/install process). You can put the initial source code/build directory wherever you want, but perhaps a directory called "sources" in your home directory would be fine.

Look at the README etc. that comes with the source code. If need be, have a look on the web for an up-to-date set of instructions or walk-through/tutorial. Report back if you encounter problems.