ReadyNAS 716: Unable to find php.ini to enable GLPI LDAP module

[gelo]

Hello everyone!

I've just installed GLPI on my readyNAS 716 (OS 6.5.1), so before I installed php5 and MySQL.

After that I launched the command find /  | grep php.ini, but there isn't any php.ini in the system.

This is the output of ls -l / is:

drwxr-xr-x 1 root root 875 Sep 26 14:26 bin
drwxr-xr-x 1 root root  54 Jul 11 19:05 frontview
drwxr-xr-x 1 root root 146 Sep  6 12:31 VOLUME1

It seems that I'm in a chroot jail.

Is there something to do to bypass this issue?

[mdgm-ntgr]

Looks like instead of logging in as 'root' (no quotes) superuser you instead logged in as a different user. The 'root' user's password is set to be the same as the one for the 'admin' user.

[gelo]

I'm always logged in as root

[mdgm-ntgr]

Well you should see a lot more directories than that in /

What's the output of the following?

# btrfs fi show
# df -h

[gelo]

root@NAS01:~# btrfs fi show
Label: '7c6ed568:root'  uuid: 7d710cab-da34-4ae1-980f-225cbcf4f088
        Total devices 1 FS bytes used 873.63MiB
        devid    1 size 4.00GiB used 3.25GiB path /dev/md0

Label: '7c6ed568:VOLUME1'  uuid: 61ad913f-b8fc-449c-809f-9196d971d941
        Total devices 1 FS bytes used 13.57GiB
        devid    1 size 14.54TiB used 16.02GiB path /dev/md127

root@NAS01:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev             10M  4.0K   10M   1% /dev
/dev/md0        4.0G  899M  2.8G  25% /
tmpfs           7.8G     0  7.8G   0% /dev/shm
tmpfs           7.8G   11M  7.8G   1% /run
tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup
tmpfs           7.8G     0  7.8G   0% /media
/dev/md127       15T   14G   15T   1% /VOLUME1
/dev/md127       15T   14G   15T   1% /home
/dev/md127       15T   14G   15T   1% /apps

[mdgm-ntgr]

Can you download the logs and send those in to me (see the Sending Logs link in my sig)?

[gelo]

wich file do you need? the entire log archive or a specific list of files?

[StephenB]

---

@gelo wrote:

wich file do you need? the entire log archive or a specific list of files?

---

They always want the full log zip.  Read his signature link, it tells you where to send them and how to associate them with this thread.

[mdgm-ntgr]

Sometimes a log one isn't expecting can be extremely important, so yes we always want the entire logs zip file. The logs provide us with information that's useful for troubleshooting a wide range of problems.

[Dom-Juan]

Hello,

I was wondering if there was a solution to this issue. I am running into the same thing at the moment.

In putty (& logged in as 'root') I can't locate the php.ini. Where should it be located, and how to find & edit the php.ini  (loaded from the offical PHP app).

Would be really nice if someone could help.

Thanks.

Juan

RN516-6x2TB-OS6.6-RAID 5 | ULTRA6-PRO-6x2TB-OS6.6-RAID 5

[FramerV]

Hi Dom-Juan,

I personally do not know where its located. I will try and inquire about this. I will be updating you once I know.

Regards,

[FramerV]

Hi Dom-Juan,

As far as I have checked the php.ini should be in /etc/php5/apache2.

Regards,

[FramerV]

Hi Dom-Juan,

We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance. 

If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” or post what resolved it and mark it as solution so others can be confident in benefiting from the solution. 
 
The Netgear community looks forward to hearing from you and being a helpful resource in the future!
 

Regards,

[Dom-Juan]

Thanks a lot for the feedback. 

I found it in two locations: 1) in apache2 directory, and 2) in the cli directory. 

It seems though that only the one in the apaches2 dir is the one to be changed. 

Maybe interesting for others:  I found  out that by accessing with Filezilla, and then editing the files locally, and push them back on the server, is a very nice way to do the job of root-editing files fromthe Readynas. 

Otherwise the issue is closed for me 🙂 

Juan.