Topic: Pydio error

[guest22]

Hi,

I've installed Pydio as per the how-to. When trying to access https://myserver.com/pydio I get the follwoing error:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<tree>
<message type="ERROR">Invalid argument supplied for foreach()</message>
</tree>

There is a /var/log/pydio directory, but it's empty.

(myserver.com is an example)

TIA
guest

[Charles2008]

I installed recently on an up-to-date SME8 (1 month ago) and all went reasonably smoothly before my server upgrade.

My install seemed perfectly functional from within the LAN. I never tried to access from WAN.
Charles

[davidS]

hi
i have the same error when i entering https://my-domain/pydio

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<tree>
<message type="ERROR">Invalid argument supplied for foreach()</message>
</tree>

is there any solution ?
thanks

[guest22]

We need to wait for Daniel. I failed in finding a (root) cause.

[Daniel B.]

hi
i have the same error when i entering https://my-domain/pydio

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<tree>
<message type="ERROR">Invalid argument supplied for foreach()</message>
</tree>

is there any solution ?
thanks

This error seems to indicate you don't have a shared folder with Pydio access enabled (or you logged on Pydio interface before enabling Pydio access on a Shared Folder). Try:

- To create a Shared Folder, be sure Pydio access is enabled
- Then run signal-event webapps-update (it will close all active sessions)

Then try again to access Pydio interface

[HomePlayer]

Hey,

I had the same error,
Daniel B. is right. After I did that i did work. SME 8.1 beta2 64bit

Only thing is, after a log in, logging out didn't work. 
I cant test now server needs to be replaced(down), and local network reworked.

[jester]

Hi,

I'm having the same trouble because i did not make a Shared Folder before accessing pydio...
Thing is though, creating a shared folder with Pydio access enabled and running "signal-event webapps-update" does not change the situation. No clues in the pydio and httpd logs. Anyone with a thought?

It's a clean SME8 (virtual) and Pydio install by the way.

[Daniel B.]

Try removing your session with

rm -f /var/lib/pydio/tmp/sess_*

And access Pydio again

[jester]

Hi Daniel,
removing the session info does not work.

[Daniel B.]

So, you installed Pydio, you login (as which user btw ?) before Pydio access was enabled on a Shared Folder, then you have enabled Pydio access on a Shared Folder, ran signal-event webapps-update and still the same error ?

Does the user you used to login has at least read access to the Shared Folder with Pydio enabled ?

[jester]

If i remember correctly the sequence was:

• Clean install SME8 and Pydio
• Try to login to Pydio as admin
• Create share with Pydio access enabled
• Created a new user
• Enable RW access to the share for that user
• Ran "signal-event webapps-update"

I've noticed a /var/lib/pydio/tmp/failedAJXP.log (don't know if related)

Code: [Select]

[root@teamshare ~]# cat /var/lib/pydio/tmp/failedAJXP.log
a:0:{}[root@teamshare ~]#

[Daniel B.]

Have you closed your browser ? first time you loggued with admin, does the admin user has access to this Shared Folder ?

[jester]

Browser has been closed (was yesterday). Cannot give admin user access to the Shared Folder (admin user does not appear under user permissions), that's why i created different user. Have only been using new user since.

[Daniel B.]

You can give the admin user access through group membership....

[jester]

• Created an administrators group and added admin user
• Set RW access to this group on the Shared Folder
• Ran:

Code: [Select]

[root@teamshare ~]# rm -f /var/lib/pydio/tmp/sess_*
[root@teamshare ~]# rm -f /var/lib/pydio/tmp/failedAJXP.log
[root@teamshare ~]# signal-event webapps-update


• New browser session
• Logged in as admin

I'm sorry to say, but still the same error.