There are a couple of minor followups between this original announcement and HEAD which improve some behaviors, but this has been in stable for about a month now.

I know this is closed, but I wanted to add how I eventually solved it. I paid more attention to my error logs (nginx), and noticed I had a permission issue. I have "wwwrun" as the nginx user, but I forgot to check /var/lib/nginx ownership; it was owned by nginx.

OK Thanks! Created T9538: HTML Emails which contain figlet and cowsay content should render respective code blocks in fixed-width font

Yeah -- at least in HTML mail, the cows aren't getting properly linebreak'd either. I don't think that's new but it should be pretty easy to fix.

@epriestley - I'm not familiar with how email should work (or how it used to) but I think figlet text (and probably cowsays) are not html-ized for html emails -- they might look better in fixed-width fontstyle but it looks like regular-type. Adding figlet text for test:

Changing the virtualhost configuration to the domain name and changing permissions in httpd.conf was sufficient. Thank you. (Still I am wondering why setting up the IP address was sufficient in another installation of Phabricator, but didn't work in this one).

I will get assistance from a friend in a few days, I will mark this ticket as solved (and explain how to solve it) as soon as we figure it out. Or comment again if we are not able to solve the problem by setting up a domain name.

Sorry, my question was are still having issues after following the guide?

Yes, because it could help solve my problem.

Is this an issue?

@epriestley @avivey That worked just fine! :)
Only thing I'm not sure about how to make 'arc unit + arc lint' disappear and just have the harbormaster builds show up in the UI.

@epriestley @avivey awesome! thanks so much for the pointers! Giving that a shot now.

@ybv: see T9365 - some of what you're seeing is just UI acting up.
Anyway, once the rdio-diff-Phabricator_Master build is complete and calls harbormaster.sendmessage, you would see the new test resultss

From what I understand, there is no way to update 'arc unit + arc lint' build plan.

From what I understand, there is no way to update 'arc unit + arc lint' build plan.

Thank you, I will look into it. Do you have any idea why this worked with the IP address on another machine (a "normal" computer, not a VM)?

Do you think, this could be the problem?

When I accessed the IP address of the VM at this point.

Have you not set up a domain name yet?

When I accessed the IP address of the VM at this point.

Thank you for your reply.

We need more information here, probably. Some step was missing or misconfigured or done out of order, perhaps, hard to guess without knowing what all you did when installing Phabricator.

Ah, I think you're right. I thought that cow just had a nice thick neck (a sign of good breeding), but her tail is a little bristly.

Does the new PHP cowsay implementation need to convert the escaped backslashes to single backslashes?

Would it be possible to get the same functionality for a footer?

It's nicer not to add things to the path variable unless necessary. Also, manually uninstalling or changing the installation directory by changing your path is more arduous than altering a line in your PS profile. Arc runs perfectly well without adding anything except PHP to the path, therefore a function is a cleaner solution for powershell-specific installation instructions.

This has been live for about a month without any followup concerns.

I haven't seen any issues related to this in the last couple of weeks. I suspect this affects <5 installs worldwide.

I think a setup warning is reasonable, particularly given that this looks like at least partially a PHP upstream configuration issue (not just one user running some weird custom-built PHP extension they wrote or whatever).

It seems you also need both display_errors and display_startup_errors turned on to hit this, though. I don't know if that is something you'd want to support.

I just hit problem (2) on this report myself, had to trace it the same way @aelam did.

sorry for the late response.
To avoid this warning set 'always_populate_raw_post_data' to '-1' in php.ini
I have known this settings, and it worked.

Closing for lack of feedback.

Going to close this out as it's not specifically a Phabricator error.

Thanks! That did it.

That error is arising from the daemons not able to create the directory for the repository. The daemons as the user specified in phd.user, or as the user running them (phd start) if you didn't specify anything. The user the daemons run as needs to own the /var/repo/ directory (Which is where Phabricator keeps repositories). You can change that by configuring repository.default-local-path (You'll need to restart the daemons).

Thanks avivey. Let me explain what I want to do, then perhaps you could help me in the best way possible.

You don't need an external domain. I use 'http://dev.macbook.local/' and update my local dns per computer accordingly. You should have more information as to what's wrong if your web server's error log.

I can't test this until I go home, since this is on my home server, and I don't think the suggested settings that the install docs work unless I get an externally registered domain name. I test on my Windows 10 box, by adding my home server's IP, pointing it to http://phabricator.thrall.com

I worked around the update issue by using

git fetch
git reset --hard 6be53bd9160807fb7c829b72b23025d233f7072c

(as suggested on the IRC)

looks related D13644

Turns out that somehow the git repository got corrupted, deleting the phabricator install and getting it from git again fixed the issue.

Yeah, even the surplus stuff is off. I'd verify your entire update process. For example, my phabricator_calendar.calendar_event table looks like this:

I don't have any other ideas. It was added in that patch, then removed a few months later in rP541e3d9e. key_room doesn't exist at HEAD.

Phabricator was installed from source using git. I can't quite remember when I last updated it, but it was probably around the end of may.

Do you know when you last updated roughly? Did you install Phabricator from source?

bin/storage status should tell you if you have patches that didn't get applied.

Why would you not just add arc to your PATH? That can be either done through the UI, or permanently via Powershell: